clear-memories

THE RISK

Critical Risk

Why clear-memories needs a policy

This tool performs an irreversible deletion of all memories in the MongoDB persistence layer. While the blast radius is limited to conversational memory data rather than production systems, the permanent loss of all accumulated context and memories represents a destructive action that cannot be undone.

From the tool's definition Tool description states 'Clear all memories from the database' - this irreversibly deletes all stored data without the ability to undo the operation.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access clear-memories gives an agent:

POLICY

How to control clear-memories

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear-memories"
  ]
}

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

Create a free account and register Memory MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Memory MCP tools

Write add-memories Add new memories to the database without overwriting existing ones Write archive-context Archive context messages for a conversation with tags and metadata Write create-summary Create a summary of context items and link them to the summary Write save-memories Save all memories to the database, overwriting existing ones Read get-conversation-summaries Get all summaries for a specific conversation Read get-memories Retrieve all memories from the database Read retrieve-context Retrieve relevant archived context for a conversation Read search-context-by-tags Search archived context and summaries by tags

All 10 Memory MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Memory MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about clear-memories

What does the clear-memories tool do? +

Clear all memories from the database. It is categorised as a Destructive tool in the Memory MCP 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 clear-memories? +

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

What risk level is clear-memories? +

clear-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 clear-memories? +

Yes. Add a rate_limit block to the clear-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 clear-memories completely? +

Set action: deny in the PolicyLayer policy for clear-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 clear-memories? +

clear-memories is provided by the Memory MCP server (jamesanz/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory MCP tool call.

Start from Memory MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →