run_complete_project_analysis · CodeBase Optimizer MCP

WHAT IT DOES

What run_complete_project_analysis does on CodeBase Optimizer

AI agents invoke run_complete_project_analysis to trigger actions in CodeBase Optimizer. 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 run_complete_project_analysis needs a policy

Although analysis tools are typically Read operations, this tool explicitly runs (executes) a comprehensive battery of checks 'in optimal order,' suggesting it triggers multiple sub-operations and processes. The term 'run' combined with 'complete' and 'all checks' indicates active execution rather than passive querying.

From the tool's definition The tool is described as a 'MASTER FUNCTION' that 'Run[s] complete project analysis with all checks in optimal order.' While ostensibly read-only (analysis), it orchestrates and executes multiple analysis operations across the codebase, including structure…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_complete_project_analysis Rate-limited

run_complete_project_analysis 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": {
    "run_complete_project_analysis": {
      "limits": [
        {
          "counter": "run_complete_project_analysis_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 CodeBase Optimizer, so you can run agents against it safely.

FAQ

Questions about run_complete_project_analysis

What does the run_complete_project_analysis tool do? +

🎯 MASTER FUNCTION: Run complete project analysis with all checks in optimal order. It is categorised as a Execute tool in the CodeBase Optimizer MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_complete_project_analysis? +

Register the CodeBase Optimizer MCP server in PolicyLayer and add a rule for run_complete_project_analysis: 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 CodeBase Optimizer. Nothing to install.

What risk level is run_complete_project_analysis? +

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

Can I rate-limit run_complete_project_analysis? +

Yes. Add a rate_limit block to the run_complete_project_analysis 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 run_complete_project_analysis completely? +

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

run_complete_project_analysis is provided by the CodeBase Optimizer MCP server (liadgez/codebase-optimizer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.