delete_corpus
Remove a saved corpus (manifest + packed body). Returns JSON: { deleted: bool, name }.
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/delete-corpus.md
What delete_corpus does on Trace
AI agents call delete_corpus 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 delete_corpus is rated Critical
This tool irreversibly deletes saved corpus data including manifest and packed body. Once removed, the corpus cannot be recovered through the tool's normal operation. While the blast radius is limited to corpus artifacts rather than production data, the destructive nature and permanent loss of potentially significant analysis artifacts (cross-language dependency graphs) justifies 'Destructive' category over 'Write'.
From the tool's definition Tool name is 'delete_corpus' and description states 'Remove a saved corpus (manifest + packed body)'. The use of 'Remove' and the operation's irreversible nature (no undo mechanism mentioned) clearly indicates data deletion.
Attacks that exploit this kind of access
The rule that runs delete_corpus 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 delete_corpus, this is the rule to start with:
delete_corpus 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 delete_corpus call is checked against it from then on.
Questions about delete_corpus
Remove a saved corpus (manifest + packed body). Returns JSON: { deleted: bool, name }. 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 delete_corpus: 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.
delete_corpus 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 delete_corpus 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 delete_corpus. 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.
delete_corpus 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