Critical Risk →

delete_memory

Delete a memory by ID

How to control delete_memory ↓

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

Critical Risk

This tool performs an irreversible deletion operation on persistent memory records. While the blast radius is somewhat contained (affects only stored memories rather than production systems), the destructive nature of data deletion without undo capability warrants the Destructive category.

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

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Roampal Core, 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.

  1. Create a free account and register Roampal Core — 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.

Go deeper

What does the delete_memory tool do? +

Delete a memory by ID. It is categorised as a Destructive tool in the Roampal Core 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 Roampal Core 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 Roampal Core. 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 Roampal Core MCP server (roampal-ai/roampal-core). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Roampal Core tool call.

Deterministic rules across all 6 Roampal Core tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

6 Roampal Core tools catalogued and risk-classified — across an index of 42,500+ 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.