Low Risk

scan_repo

Check if your app is ready to ship. Triggers a production readiness scan on a GitHub repository, analyzing security, deployment, stability, tests, and UI completeness. Returns a prioritized finish plan with all findings. Use when a user asks 'is my app ready?', 'what do I need before launch?', or...

Part of the Finishkit MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call scan_repo to retrieve information from Finishkit without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though scan_repo only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-finishkit-mcp.yaml
tools:
  scan_repo:
    rules:
      - action: allow

See the full Finishkit policy for all 9 tools.

Tool Name scan_repo
Category Read
Risk Level Low

View all 9 tools →

Agents calling read-class tools like scan_repo have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the scan_repo tool do? +

Check if your app is ready to ship. Triggers a production readiness scan on a GitHub repository, analyzing security, deployment, stability, tests, and UI completeness. Returns a prioritized finish plan with all findings. Use when a user asks 'is my app ready?', 'what do I need before launch?', or 'check production readiness'. Typically takes 2-8 minutes.. It is categorised as a Read tool in the Finishkit MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scan_repo? +

Add a rule in your Intercept YAML policy under the tools section for scan_repo. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Finishkit MCP server.

What risk level is scan_repo? +

scan_repo is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit scan_repo? +

Yes. Add a rate_limit block to the scan_repo rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block scan_repo completely? +

Set action: deny in the Intercept policy for scan_repo. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides scan_repo? +

scan_repo is provided by the Finishkit MCP server (@finishkit/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Finishkit

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.