delete_project_memory

THE RISK

Critical Risk

Why delete_project_memory needs a policy

The tool performs irreversible deletion of project memory records. Even though the description is empty, the explicit use of 'delete' in the name combined with the context of a project management memory system makes this clearly a Destructive operation. An AI agent misusing this could permanently erase project data without recovery options.

From the tool's definition Tool name is 'delete_project_memory'; sibling tool 'delete_all_project_memories' confirms this server includes irreversible deletion capabilities. Description is empty, but the name unambiguously indicates permanent removal of data.

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

POLICY

How to control delete_project_memory

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

policy.json

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

delete_project_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 mem0 MCP Server for Project Management — 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 mem0 MCP Server for Project Management tools

Destructive delete_all_project_memories Delete multiple project memories based on specified filters. This tool uses the delete_all Write add_project_memory add_project_memory Write update_project_memory update_project_memory Read get_all_project_memories get_all_project_memories Read search_project_memories search_project_memories

All 6 mem0 MCP Server for Project Management 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 mem0 MCP Server for Project Management → 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_project_memory

What does the delete_project_memory tool do? +

delete_project_memory. It is categorised as a Destructive tool in the mem0 MCP Server for Project Management 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_project_memory? +

Register the mem0 MCP Server for Project Management MCP server in PolicyLayer and add a rule for delete_project_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 mem0 MCP Server for Project Management. Nothing to install.

What risk level is delete_project_memory? +

delete_project_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_project_memory? +

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

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

delete_project_memory is provided by the mem0 MCP Server for Project Management MCP server (kunihiros/mem0-mcp-for-pm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every mem0 MCP Server for Project Management tool call.

Start from mem0 MCP Server for Project Management, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →