Delete a memory entry and all its version backups
AI agents call delete_memory to permanently remove resources in Claude Memory MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes stored memories without the ability to undo the operation. Although the server provides backup/restore functionality, the delete_memory tool itself performs an irreversible destruction of data. The presence of version backups being deleted alongside the primary entry confirms the destructive nature.
From the tool's definition 'Delete a memory entry and all its version backups' — the tool irreversibly removes data and explicitly purges all historical versions, preventing recovery.
Attacks that exploit this kind of access
Delete a memory entry and all its version backups. It is categorised as a Destructive tool in the Claude Memory MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Memory MCP Server MCP server in PolicyLayer and add a rule for delete_memory: 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 Memory MCP Server. Nothing to install.
delete_memory 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_memory 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_memory. 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_memory is provided by the Claude Memory MCP Server MCP server (seongcheoljeon/claudememorymcp). 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 →