Find potentially unused code in project
AI agents call find_dead_code to retrieve information from Claude MCP Server Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes project code to identify dead code patterns, which is a query/analysis operation with no side effects, no execution, and no data modification. It belongs in the Read category as it only provides information about the codebase. Low severity because misuse would only yield incorrect analysis results, not cause harm to systems or data.
From the tool's definition Tool performs analysis to 'find potentially unused code' - a read-only operation that scans and reports on code patterns without modifying or executing any code.
Attacks that exploit this kind of access
Find potentially unused code in project. It is categorised as a Read tool in the Claude MCP Server Integration MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for find_dead_code: 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 Claude MCP Server Integration. Nothing to install.
find_dead_code 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 find_dead_code 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 find_dead_code. 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.
find_dead_code is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). 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 →