Critical Risk →

delete

delete

How to control delete ↓

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

Critical Risk

The 'delete' tool removes data from persistent memory storage without reversal capability. Even though the description is empty, the name combined with the memory management context (recording, retrieval, updating memories) strongly indicates this performs irreversible deletion.

From the tool's definition Tool named 'delete' on a memory store server; sibling tools include 'delete_memory' and 'update', indicating this tool irreversibly removes stored data. Empty description limits confidence but the name and context are unambiguous.

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

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

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

delete 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 Memory-Plus — 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 tool do? +

delete. It is categorised as a Destructive tool in the Memory-Plus 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? +

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

What risk level is delete? +

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

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

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

delete is provided by the Memory-Plus MCP server (yuchen20/memory-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory-Plus tool call.

Deterministic rules across all 14 Memory-Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

14 Memory-Plus 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.