DELETE REMOVE FORGET ERASE - Delete a specific memory by ID. Keywords: delete, remove, forget, erase, clear, purge, discard, eliminate, destroy memory, remove fact, forget information
AI agents call memory_delete to permanently remove resources in MCP AI Memory — 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 memory records. Once a memory is deleted by ID, it cannot be recovered from the persistent PostgreSQL vector store. While not financial or system-level destructive, it is destructive in nature as it permanently removes data that an AI agent might depend on for context continuity.
From the tool's definition Tool name is 'memory_delete' with description explicitly stating 'DELETE REMOVE FORGET ERASE - Delete a specific memory by ID' and including keywords 'delete, remove, forget, erase, clear, purge, discard, eliminate, destroy memory'.
Documented attack patterns abuse exactly the kind of access memory_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP AI Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_delete:
{
"version": "1",
"default": "deny",
"hide": [
"memory_delete"
]
}memory_delete 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.
DELETE REMOVE FORGET ERASE - Delete a specific memory by ID. Keywords: delete, remove, forget, erase, clear, purge, discard, eliminate, destroy memory, remove fact, forget information. It is categorised as a Destructive tool in the MCP AI Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP AI Memory MCP server in PolicyLayer and add a rule for memory_delete: 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 MCP AI Memory. Nothing to install.
memory_delete 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 memory_delete 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 memory_delete. 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.
memory_delete is provided by the MCP AI Memory MCP server (scanadi/mcp-ai-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 MCP AI Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 MCP AI Memory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.