Analyze complexity metrics for a specific file
AI agents call analyze-complexity to retrieve information from Debugger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis and metric collection on a file, returning insights about its complexity (e.g., cyclomatic complexity, cognitive complexity). It does not modify code, execute arbitrary commands, delete data, or trigger external side effects. It is purely diagnostic and informational, fitting the Read category with low severity due to its non-invasive nature and limited blast radius if misused.
From the tool's definition Tool is described as 'Analyze complexity metrics for a specific file' — a passive analysis operation that retrieves and reports code quality data without modifying state or executing code.
Attacks that exploit this kind of access
Analyze complexity metrics for a specific file. It is categorised as a Read tool in the Debugger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for analyze-complexity: 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 Debugger MCP Server. Nothing to install.
analyze-complexity is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the analyze-complexity 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.
Set action: deny in the PolicyLayer policy for analyze-complexity. 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.
analyze-complexity is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →