Ranked list of functions/methods by cyclomatic complexity. Useful for identifying refactoring candidates.
AI agents call complexity_hotspots to retrieve information from code-intel 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 queries code metrics—retrieving and ranking data about code structure. It has no side effects, does not execute code, and does not create or modify files. It is purely informational, making it a Read operation with minimal risk.
From the tool's definition Tool returns a 'ranked list' of code metrics (cyclomatic complexity); it 'identifies refactoring candidates' through analysis, with no capability to modify, delete, or execute code.
Attacks that exploit this kind of access
Ranked list of functions/methods by cyclomatic complexity. Useful for identifying refactoring candidates. It is categorised as a Read tool in the code-intel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the code-intel MCP Server MCP server in PolicyLayer and add a rule for complexity_hotspots: 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 code-intel MCP Server. Nothing to install.
complexity_hotspots 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 complexity_hotspots 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 complexity_hotspots. 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.
complexity_hotspots is provided by the code-intel MCP Server MCP server (vohongtho/code-intel-platform). 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 →