Aikido MCP scan hits the 50-file limit - batch requests and re-scan after fixes
Aikido MCP scan hits the 50-file limit - batch requests and re-scan after fixes: Per the Aikido scan skill: batch scans to 50 files per call and re-scan after each fix round, stopping after 3 attempts.
Per the Aikido scan skill: batch scans to 50 files per call and re-scan after each fix round, stopping after 3 attempts.
Context: Problem: Scanning a large change set with the Aikido MCP tools fails or truncates. Stay within the 50-file limit per request and batch bigger scans into multiple calls. After applying the remediations, re-run the same scan tool to verify the issues are resolved and no new ones appeared. Repeat the fix-and-rescan cycle up to 3 attempts; if issues remain, report them instead of looping forever. If the MCP server is not available or fails to start, run /aikido:setup to configure it.
Matched source
Source: Source: https://github.com/aikidosec/aikido-cursor-plugin/blob/HEAD/skills/scan/SKILL.md Original query: "Aikido MCP scan hits the 50-file limit - batch requests and re-scan after fixes" Key terms: after, aikido, batch, file, fixes, hits, limit, requests, scan
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.