Delete a memory by its ID. Use during reconciliation to remove an outdated
AI agents call delete_memory to permanently remove resources in Mem0 Mcp Toggle — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (a memory record) from the local Chroma storage by ID. Deletion operations that cannot be undone fall into the Destructive category. While the blast radius is somewhat limited to locally-stored memories rather than shared systems, an AI agent could still misuse this to delete important memory records without user intent, causing information loss.
From the tool's definition Tool name is 'delete_memory' and description states 'Delete a memory by its ID', which is an irreversible deletion operation.
Attacks that exploit this kind of access
Delete a memory by its ID. Use during reconciliation to remove an outdated. It is categorised as a Destructive tool in the Mem0 Mcp Toggle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mem0 Mcp Toggle 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 Mcp Toggle. 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 Toggle MCP server (ost527/mem0-mcp-toggle). 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 →