delete_all_memories

THE RISK

Critical Risk

This tool permanently deletes memory records without a reversible operation. Batch deletion of 'all' memories for a given user/agent/run represents irreversible data loss. The blast radius is high because an agent misconfigured or compromised could erase all historical context and user data. This is more severe than Write (which is reversible) and qualifies as Destructive.

From the tool's definition Tool name is 'delete_all_memories' with description 'Batch delete memories'. The verb 'delete' combined with 'all' indicates irreversible removal of data at scale.

Risk signalsBulk/mass operation — affects multiple targets

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

HOW TO CONTROL DELETE_ALL_MEMORIES

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

policy.json

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

delete_all_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 Mcp Oceanbase — 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

More Mcp Oceanbase tools

Destructive delete_backup_policy delete_backup_policy Destructive delete_cluster 删除指定命名空间中的OceanBase集群 Args: cluster_name: 要删除的集群名称 namespace: 要从中删除集群 Destructive delete_collection Delete a collection from seekdb. This will permanently delete the collection and all Destructive delete_documents delete_documents Destructive delete_memory Delete memory Args: memory_id: Memory ID user_id: User identifier Destructive delete_memory_with_profile Delete memory and optionally the associated user profile Args: memory_id: Mem Destructive delete_tenant delete_tenant Destructive delete_user_profile Delete user profile by user_id Removes the user profile from storage. This does not d

All 134 Mcp Oceanbase tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Mcp Oceanbase → 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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete_all_memories tool do? +

Batch delete memories Args: user_id: User identifier agent_id: Agent identifier run_id: Run/session identifier Returns: JSON formatted string. It is categorised as a Destructive tool in the Mcp Oceanbase 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_memories? +

Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for delete_all_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 Mcp Oceanbase. Nothing to install.

What risk level is delete_all_memories? +

delete_all_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_memories? +

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

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

delete_all_memories is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Oceanbase tool call.

Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP OCEANBASE →

Free to start. No card required.

134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT DELETE_ALL_MEMORIES ON MCP OCEANBASE DOES

// THE RISK

// HOW TO CONTROL DELETE_ALL_MEMORIES

// EXPLORE