Analyze code complexity: functions, classes, nesting depth, cyclomatic complexity.
AI agents call analyze_complexity to retrieve information from DevToolkit 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 of code structure to compute complexity metrics. It retrieves and reports information about code characteristics without executing code, modifying files, or triggering side effects. Analysis-only operations without code execution fall squarely into the Read category.
From the tool's definition Tool analyzes code metrics (functions, classes, nesting depth, cyclomatic complexity) with no modification or execution capability. The verb 'analyze' and the focus on metric computation confirms read-only data retrieval.
Attacks that exploit this kind of access
Analyze code complexity: functions, classes, nesting depth, cyclomatic complexity. It is categorised as a Read tool in the DevToolkit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevToolkit 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 DevToolkit 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 DevToolkit MCP Server MCP server (tusharrayamajhi/devtoolkit-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 →