Critical Risk →

delete_all_memories

delete_all_memories

How to control delete_all_memories ↓

What delete_all_memories does on RememberMe

AI agents call delete_all_memories to permanently remove resources in RememberMe — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_all_memories needs a policy

This tool irreversibly deletes all user memories without the ability to undo or recover the data. The blast radius is high because it eliminates the entire memory context for a user or session, potentially compromising the utility and continuity of the client's interaction history. The destructive category takes precedence over Write (its parent is clearly delete, not create/update).

From the tool's definition Tool name 'delete_all_memories' combined with sibling tool 'delete_memory' indicates irreversible deletion of all stored memory records. No description provided, but the name unambiguously conveys a destructive operation affecting the entire memory store.

Documented attack patterns abuse exactly the kind of access delete_all_memories gives an agent:

How to control delete_all_memories

PolicyLayer is an MCP gateway — it sits between your AI agents and RememberMe, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_all_memories:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_all_memories"
  ]
}

delete_all_memories disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register RememberMe — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_all_memories

What does the delete_all_memories tool do? +

delete_all_memories. It is categorised as a Destructive tool in the RememberMe MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_all_memories? +

Register the RememberMe MCP server in PolicyLayer and add a rule for delete_all_memories: 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 RememberMe. Nothing to install.

What risk level is delete_all_memories? +

delete_all_memories is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_all_memories? +

Yes. Add a rate_limit block to the delete_all_memories 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.

How do I block delete_all_memories completely? +

Set action: deny in the PolicyLayer policy for delete_all_memories. 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.

What MCP server provides delete_all_memories? +

delete_all_memories is provided by the RememberMe MCP server (joexie/remember-me). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RememberMe tool call.

Start from RememberMe, 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.

6 RememberMe tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.