Delete a memory by its key. This action is permanent and cannot be undone. Args: key: The unique identifier of the memory to delete.
AI agents call delete_memory to permanently remove resources in ContextKeep — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes stored data without recovery options. While the blast radius is limited to the user's own memory store (not system-wide), deletion of stored project details, preferences, or snippets could cause significant operational disruption if an AI agent misuses it—e.g., deleting critical project context.
From the tool's definition Tool description explicitly states 'This action is permanent and cannot be undone.' The function deletes memory records by key, and the description confirms irreversibility.
Documented attack patterns abuse exactly the kind of access delete_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ContextKeep, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_memory:
{
"version": "1",
"default": "deny",
"hide": [
"delete_memory"
]
}delete_memory 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 a memory by its key. This action is permanent and cannot be undone. Args: key: The unique identifier of the memory to delete. It is categorised as a Destructive tool in the ContextKeep MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ContextKeep 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 ContextKeep. 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 ContextKeep MCP server (mordang7/contextkeep). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ContextKeep, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 ContextKeep tools catalogued and risk-classified — across an index of 43,000+ MCP servers.