Find functions, methods, and classes that are never called by anything in the graph. Useful before refactors or cleanups. Common entry-point patterns (main, init, onX, handleX, etc.) are filtered out by default.
AI agents call find_dead_code to retrieve information from GraphHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure analysis tool that queries the knowledge graph to identify unreachable code patterns. It retrieves and reports information without creating, modifying, deleting, or executing any code. The filtering of entry-point patterns is a display/presentation concern, not a state-altering operation.
From the tool's definition The tool 'find_dead_code' analyzes a codebase graph to identify unused functions, methods, and classes. The description explicitly states it finds code that is 'never called,' indicating it performs analysis and retrieval without modifying or executing…
Documented attack patterns abuse exactly the kind of access find_dead_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GraphHub, and nothing reaches the server without passing your rules. This is the rule we recommend for find_dead_code:
{
"version": "1",
"default": "deny",
"tools": {
"find_dead_code": {}
}
}find_dead_code is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find functions, methods, and classes that are never called by anything in the graph. Useful before refactors or cleanups. Common entry-point patterns (main, init, onX, handleX, etc.) are filtered out by default. It is categorised as a Read tool in the GraphHub MCP Server, which means it retrieves data without modifying state.
Register the GraphHub 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 GraphHub. 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 GraphHub MCP server (slnquangtran/graph-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GraphHub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 GraphHub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.