delete_memory

THE RISK

Critical Risk

Why delete_memory needs a policy

This tool irreversibly removes data from persistent storage (memories in a Qdrant vector database). While the blast radius is contained to a single memory entry rather than bulk deletion, it cannot be undone and represents a destructive action.

From the tool's definition The tool description explicitly states 'Delete a specific memory by its ID', which is an irreversible deletion operation.

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 MCP Qdrant Semantic Search, 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 MCP Qdrant Semantic Search — 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 MCP Qdrant Semantic Search tools

Destructive clear_all_memories Delete ALL memories from the collection. ⚠️ Warning: this action is irreversible! Write store_memory Store information in semantic memory. The information will be indexed and can be retrieved Read get_memory Retrieve a specific memory by its ID with all its details. Read get_stats Get statistics about the memory collection (total count, status, etc.). Read list_memories List all stored memories with pagination. Useful for exploring database content. Read search_memory Search for semantically similar information in memory. Returns the most relevant results b

All 7 MCP Qdrant Semantic Search 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 MCP Qdrant Semantic Search → 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 specific memory by its ID. The ID is returned when storing a memory. It is categorised as a Destructive tool in the MCP Qdrant Semantic Search 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 MCP Qdrant Semantic Search 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 MCP Qdrant Semantic Search. 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 MCP Qdrant Semantic Search MCP server (muhammedehab35/mcp-qdrant-semantic-search). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Qdrant Semantic Search tool call.

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

CHECK YOUR STACK →