Classify every callable / type in the indexed graph as live, dead, or unreachable-export and return the non-live set. Also surfaces ghost communities — Leiden clusters whose every member is classified non-live.
AI agents call list_dead_code to retrieve information from OpenCodeHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_dead_code retrieves and returns analysis results (classification of code as live/dead/unreachable) from the indexed knowledge graph. It has no side effects, does not execute code, does not modify repositories, and does not delete or overwrite data. It is purely a read-based intelligence/query operation typical of code analysis tools.
From the tool's definition Tool is described as 'Classify every callable / type in the indexed graph as live, dead, or unreachable-export and return the non-live set.' This is a query and analysis operation over existing code metadata.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Classify every callable / type in the indexed graph as live, dead, or unreachable-export and return the non-live set. Also surfaces ghost communities — Leiden clusters whose every member is classified non-live. It is categorised as a Read tool in the OpenCodeHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenCodeHub MCP Server MCP server in PolicyLayer and add a rule for list_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 OpenCodeHub MCP Server. Nothing to install.
list_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 list_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 list_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.
list_dead_code is provided by the OpenCodeHub MCP Server MCP server (theagenticguy/opencodehub). 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 →