Aikido MCP scan hits the 50-file limit - batch requests and re-scan after fixes

TL;DR

Per the Aikido scan skill: batch scans to 50 files per call and re-scan after each fix round, stopping after 3 attempts. After applying the remediations, re-run the same scan tool to verify the issues are resolved and no new ones appeared.

Steps

1. Per the Aikido scan skill: batch scans to 50 files per call and re-scan after each fix round, stopping after 3 attempts.
2. After applying the remediations, re-run the same scan tool to verify the issues are resolved and no new ones appeared.

When to use

You are seeing this: Stay within the 50-file limit per request and batch bigger scans into multiple calls. Use this skill when you run into "Aikido MCP scan hits the 50-file limit - batch requests and re-scan after fixes".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: 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.

Verified resolution: Per the Aikido scan skill: batch scans to 50 files per call and re-scan after each fix round, stopping after 3 attempts.

Source URL: https://github.com/aikidosec/aikido-cursor-plugin/blob/HEAD/skills/scan/SKILL.md