delete_all_project_memories

WHAT IT DOES

What delete_all_project_memories does on mem0 MCP Server for Project Management

AI agents call delete_all_project_memories to permanently remove resources in mem0 MCP Server for Project Management — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why delete_all_project_memories needs a policy

This tool irreversibly deletes data without the ability to undo the operation. The warning about deleting ALL memories if no filters are specified elevates the risk to high severity, as a misconfiguration or misuse by an AI agent could result in catastrophic data loss. Destructive is the most severe applicable category and takes precedence over Write.

From the tool's definition The tool is explicitly named 'delete_all_project_memories' and the description states 'Delete multiple project memories' and 'will delete ALL memories that match the specified filters.' The description further warns 'If no filters are specified, it could…

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

POLICY

How to control delete_all_project_memories

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_all_project_memories:

policy.json

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

delete_all_project_memories 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_project_memory delete_project_memory 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_all_project_memories

What does the delete_all_project_memories tool do? +

Delete multiple project memories based on specified filters. This tool uses the delete_all method to remove multiple memories based on filter criteria. IMPORTANT: Use this tool with caution as it will delete ALL memories that match the specified filters. If no filters are specified, it could potentially delete ALL memories. Args: user_id (str, optional): Filter memories by user ID. agent_id (str, optional): Filter memories by agent ID. app_id (str, optional): Filter memories by app ID. run_id (str, optional): Filter memories by run ID. metadata (dict, optional): Filter memories by metadata. org_id (str, optional): Filter memories by organization ID. project_id (str, optional): Filter memories by project ID. Returns: str: A success message if the memories were deleted successfully, or an error message if there was an issue. 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_all_project_memories? +

Register the mem0 MCP Server for Project Management MCP server in PolicyLayer and add a rule for delete_all_project_memories: 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_all_project_memories? +

delete_all_project_memories 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_all_project_memories? +

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

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

delete_all_project_memories 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.