delete_memory
AI agents call delete_memory to permanently remove resources in Mem0 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name 'delete_memory' strongly indicates deletion of data, which is irreversible. Without a description, we rely on the semantic meaning: 'delete' is a destructive action. In the context of a memory management API, this would remove stored context/data that cannot be undone. This is more severe than Write (which is reversible modification) and qualifies as Destructive.
From the tool's definition Tool named 'delete_memory' with no description provided. Based on naming convention and sibling tools (add_memory, erase_memories, get_memory, list_memories, search_memories, update_memory), this tool irreversibly removes stored memory data.
Attacks that exploit this kind of access
delete_memory. It is categorised as a Destructive tool in the Mem0 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mem0 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 Mem0. 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 Mem0 MCP server (olk/mem0-mcp-server). 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 →