analyze_project · MCP Code Analyzer MCP: Risk & Policy

WHAT IT DOES

What analyze_project does on MCP Code Analyzer

AI agents invoke analyze_project to trigger actions in MCP Code Analyzer. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why analyze_project needs a policy

This tool orchestrates multiple external tools (Semgrep, ESLint, CLI commands) to scan and analyze a codebase. It triggers external operations whose effects depend on arguments, classifying it as Execute. Severity is high because it runs arbitrary scanning tools against a project, potentially exposing sensitive code details, consuming significant resources, or being misused to analyze unintended targets.

From the tool's definition 'Analyze a code project' by coordinating tools like Semgrep and ESLint, performing 'vulnerability scanning, architecture metrics, and impact analysis through CLI'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

analyze_project Rate-limited

analyze_project stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_project": {
      "limits": [
        {
          "counter": "analyze_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Code Analyzer, so you can run agents against it safely.

FAQ

Questions about analyze_project

What does the analyze_project tool do? +

Analyze a code project for security, quality, dependencies, and architecture issues. It is categorised as a Execute tool in the MCP Code Analyzer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on analyze_project? +

Register the MCP Code Analyzer MCP server in PolicyLayer and add a rule for analyze_project: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP Code Analyzer. Nothing to install.

What risk level is analyze_project? +

analyze_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit analyze_project? +

Yes. Add a rate_limit block to the analyze_project rule in your PolicyLayer 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 analyze_project completely? +

Set action: deny in the PolicyLayer policy for analyze_project. 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 analyze_project? +

analyze_project is provided by the MCP Code Analyzer MCP server (polocap/mcp_security). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.