reset_memory

THE RISK

Critical Risk

Why reset_memory needs a policy

This tool irreversibly deletes all data in the memory system (notes, edges, embeddings) with no recovery mechanism. The description's explicit warning about being unable to undo this action confirms it is destructive. Combined with the scale of data affected (complete memory system), this poses a critical risk if triggered by an agent without proper safeguards.

From the tool's definition Tool description explicitly states: 'Resets the complete memory system (Graph + Vector Store). Deletes all notes, edges, and embeddings.' and includes warning 'This action cannot be undone!'

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

POLICY

How to control reset_memory

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_memory"
  ]
}

reset_memory 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 A-MEM: Agentic Memory System — 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 A-MEM: Agentic Memory System tools

Destructive delete_atomic_note Deletes a note from the memory system. Removes the note from Graph and Vector Store as wel Destructive remove_relation Removes a relation between two notes. Execute run_memory_enzymes Runs comprehensive memory maintenance enzymes: repairs corrupted nodes, prunes old/weak li Execute research_and_store Performs deep web research on a query and stores the findings as atomic notes. Uses Google Write add_file Stores the content of a file (e.g., .md) as a note in the memory system. Supports automati Write add_relation Adds a manual relation between two notes. Write create_atomic_note Stores a new piece of information in the memory system. Automatically classifies the note Write update_note Updates contextual summary, tags or keywords for an existing note.

All 15 A-MEM: Agentic Memory System 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 A-MEM: Agentic Memory System → 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 reset_memory

What does the reset_memory tool do? +

Resets the complete memory system (Graph + Vector Store). Deletes all notes, edges, and embeddings. WARNING: This action cannot be undone!. It is categorised as a Destructive tool in the A-MEM: Agentic Memory System 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 reset_memory? +

Register the A-MEM: Agentic Memory System MCP server in PolicyLayer and add a rule for reset_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 A-MEM: Agentic Memory System. Nothing to install.

What risk level is reset_memory? +

reset_memory 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 reset_memory? +

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

How do I block reset_memory completely? +

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

What MCP server provides reset_memory? +

reset_memory is provided by the A-MEM: Agentic Memory System MCP server (tobs-code/a-mem-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every A-MEM: Agentic Memory System tool call.

Start from A-MEM: Agentic Memory System, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →