This tool deletes a specific memory by its ID from the current namespace. Use when you need to remove outdated or incorrect information.
AI agents call deleteMemory to permanently remove resources in MCP Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (memory entries) and cannot be undone. Deletion is irreversible, fitting the Destructive category. While the blast radius is limited to user memory/preference data rather than critical systems, an AI agent could maliciously or erroneously delete important user information, historical context, or preferences that were essential to ongoing conversations.
From the tool's definition Tool description states 'deletes a specific memory by its ID' and 'remove outdated or incorrect information.' The tool name 'deleteMemory' and verb 'deletes' directly indicate irreversible data removal.
Attacks that exploit this kind of access
This tool deletes a specific memory by its ID from the current namespace. Use when you need to remove outdated or incorrect information. It is categorised as a Destructive tool in the MCP Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Memory MCP server in PolicyLayer and add a rule for deleteMemory: 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 Memory. Nothing to install.
deleteMemory 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 deleteMemory 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 deleteMemory. 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.
deleteMemory is provided by the MCP Memory MCP server (redaphid/mcp-memory). 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 →