delete_memory

THE RISK

Critical Risk

Why delete_memory needs a policy

This tool performs an irreversible deletion operation on memory records within an AI memory management system. Deletion of memories cannot be undone and represents a destructive action on stored data. The high severity reflects that an AI agent could inadvertently or maliciously erase important contextual information, cached decisions, or historical records that other systems or future interactions depend on.

From the tool's definition Tool name is 'delete_memory' with description 'Delete a memory'. The verb 'delete' combined with 'memory' indicates irreversible removal of stored data.

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

POLICY

How to control delete_memory

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

policy.json

{
  "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.

Create a free account and register SAM — 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 SAM tools

Execute trigger_auto_analysis Manually trigger automatic analysis of conversation Write cascade_interaction Log interaction with Windsurf Cascade AI Write cursor_code_assist Log Cursor AI code assistance interactions with auto-memory Write log_collaboration Log collaboration activities in a Repl Write auto_save_memory Automatically save memory if content triggers the threshold Write configure_triggers Configure automatic trigger settings Write cursor_project_context Update project context and learning patterns Write cursor_session_summary Generate and save Cursor session summary with learnings

All 37 SAM 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 SAM → 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 delete_memory

What does the delete_memory tool do? +

Delete a memory. It is categorised as a Destructive tool in the SAM 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_memory? +

Register the SAM 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 SAM. Nothing to install.

What risk level is delete_memory? +

delete_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 delete_memory? +

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.

How do I block delete_memory completely? +

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.

What MCP server provides delete_memory? +

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

Enforce policy on every SAM tool call.

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

CHECK YOUR STACK →