Securely wipe ALL Claude Code traces. Overwrites files with zeros before deletion. Requires explicit confirmation.
AI agents call wipe_traces to permanently remove resources in Claude Code Toolkit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently and irreversibly deletes data (traces) with overwriting for security. Even though it requires explicit confirmation (a mitigating control), the core action is destructive — it cannot be undone. The high severity reflects that losing all Claude Code traces could impact observability, debugging, auditing, and compliance.
From the tool's definition The tool description explicitly states it will "Securely wipe ALL Claude Code traces" and "Overwrites files with zeros before deletion." The use of "wipe," "ALL," and multi-step deletion confirms irreversible data destruction.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access wipe_traces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for wipe_traces:
{
"version": "1",
"default": "deny",
"hide": [
"wipe_traces"
]
}wipe_traces disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Securely wipe ALL Claude Code traces. Overwrites files with zeros before deletion. Requires explicit confirmation. It is categorised as a Destructive tool in the Claude Code Toolkit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for wipe_traces: 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 Claude Code Toolkit. Nothing to install.
wipe_traces 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 wipe_traces 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 wipe_traces. 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.
wipe_traces is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, 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.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.