remove_dead_code
Safely remove a dead symbol from its file. Verifies the symbol is actually dead (multi-signal detection or zero incoming edges) before removal. Warns about orphaned imports in other files. Dry-run by default — preview the plan, then re-call with dry_run: false to apply. Destructive when applied —...
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/remove-dead-code.md
What remove_dead_code does on Trace
AI agents call remove_dead_code to permanently remove resources in Trace, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_dead_code is rated Critical
This tool irreversibly removes code (dead symbols) from source files. While it includes safety mechanisms (verification, dry-run mode by default, orphan detection), the actual operation deletes data that cannot be undone. The tool requires explicit opt-in to apply changes (dry_run: false), but once executed, the deletion is permanent. This makes it Destructive rather than Write.
From the tool's definition Destructive when applied — deletes code from source files.
Attacks that exploit this kind of access
The rule that runs remove_dead_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_dead_code, this is the rule to start with:
remove_dead_code is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every remove_dead_code call is checked against it from then on.
Questions about remove_dead_code
Safely remove a dead symbol from its file. Verifies the symbol is actually dead (multi-signal detection or zero incoming edges) before removal. Warns about orphaned imports in other files. Dry-run by default — preview the plan, then re-call with dry_run: false to apply. Destructive when applied — deletes code from source files. Use get_dead_code first to identify candidates. Returns JSON: { success, removed: { symbol_id, file }, orphanedImports }. It is categorised as a Destructive tool in the Trace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Trace MCP server in PolicyLayer and add a rule for remove_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 Trace. Nothing to install.
remove_dead_code is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_dead_code is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
Across the catalogue