Delete a specific memory by its ID.
AI agents call delete_memory to permanently remove resources in Memory MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of data from the SQLite-backed memory system. Once a memory is deleted by ID, it cannot be recovered through normal operation. In the context of a coding assistant with persistent cross-session memory, deleting memories could cause loss of critical project context, architectural decisions, or important conversation history.
From the tool's definition Tool name explicitly states 'delete_memory' and description confirms 'Delete a specific memory by its ID.' The action irreversibly removes stored data (project context, decisions, preferences, conversation history) from the persistent store.
Attacks that exploit this kind of access
Delete a specific memory by its ID. It is categorised as a Destructive tool in the Memory MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Memory 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 Memory MCP. 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 Memory MCP server (nerdyaustin/memory_mcp). 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 →