Delete memory Args: memory_id: Memory ID user_id: User identifier agent_id: Agent identifier Returns: JSON formatted string
AI agents call delete_memory to permanently remove resources in Mcp Oceanbase — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes memory records without the ability to undo the action. Deletion operations that cannot be reversed fall into the Destructive category. The severity is high because an AI agent invoking this with incorrect memory_id or user_id could permanently erase important user or agent memory, affecting system state and potentially causing data loss.
From the tool's definition Tool name is 'delete_memory' and description states 'Delete memory'. The function signature includes memory_id, user_id, and agent_id parameters, indicating targeted deletion of stored memory records.
Documented attack patterns abuse exactly the kind of access delete_memory gives an agent:
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_memory:
{
"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.
Free to start. No card required.
Delete memory Args: memory_id: Memory ID user_id: User identifier agent_id: Agent 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.
Register the Mcp Oceanbase 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 Oceanbase. Nothing to install.
delete_memory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
delete_memory 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.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.