New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_corpus

Remove a saved corpus (manifest + packed body). Returns JSON: { deleted: bool, name }.

SERVERTrace SOURCEnikolai-vysotskyi/trace-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_corpus

What does the delete_corpus tool do? +

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.

How do I enforce a policy on delete_corpus? +

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.

What risk level is delete_corpus? +

delete_corpus is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_corpus? +

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.

How do I block delete_corpus completely? +

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.

What MCP server provides delete_corpus? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Trace's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.