Delete a memory file at /memories/<path>. When the path ends with /, every file beneath the directory is removed. Updates the path index but leaves prior content-addressed blobs in place (the audit history is append-only). Mirrors the delete verb in Anthropic's context-management-2025-06-27 memor...
Risk signalsAccepts file system path (path) · Bulk/mass operation — affects multiple targets
Part of the emem — Earth memory protocol server.
Free to start. No card required.
AI agents may call memory_delete to permanently remove or destroy resources in emem — Earth memory protocol. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call memory_delete in a loop, permanently destroying resources in emem — Earth memory protocol. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"memory_delete"
]
}See the full emem — Earth memory protocol policy for all 81 tools.
These attack patterns abuse exactly the kind of access memory_delete gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Delete a memory file at /memories/<path>. When the path ends with /, every file beneath the directory is removed. Updates the path index but leaves prior content-addressed blobs in place (the audit history is append-only). Mirrors the delete verb in Anthropic's context-management-2025-06-27 memory tool spec. When to use: Call when the LLM issues a delete against a memory file or subdirectory it no longer needs. Existing receipts citing the old file_cid stay verifiable — the blob is content-addressed, only the path → file_cid index forgets.. It is categorised as a Destructive tool in the emem — Earth memory protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the emem — Earth memory protocol 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 emem — Earth memory protocol. 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 emem — Earth memory protocol MCP server (oci:ghcr.io/vortx-ai/emem:latest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 81 emem — Earth memory protocol tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.