Delete a collection from seekdb. This will permanently delete the collection and all its data. This operation cannot be undone. Args: collection_name: The name of the collection to delete. The collection must exist. Returns: A JSON string indicating success or error.
AI agents call delete_collection 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 irreversibly deletes data (a collection and all its contents). The description confirms the action cannot be reversed. This meets the definition of Destructive category. Severity is high because misuse by an AI agent could result in permanent loss of potentially important data, though the impact is scoped to a single collection rather than an entire system (which would be critical).
From the tool's definition 'Delete a collection from seekdb. This will permanently delete the collection and all its data. This operation cannot be undone.' The description explicitly states the operation is permanent and cannot be undone, which is the defining characteristic of…
Documented attack patterns abuse exactly the kind of access delete_collection 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_collection:
{
"version": "1",
"default": "deny",
"hide": [
"delete_collection"
]
}delete_collection 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 a collection from seekdb. This will permanently delete the collection and all its data. This operation cannot be undone. Args: collection_name: The name of the collection to delete. The collection must exist. Returns: A JSON string indicating success or error. 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_collection: 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_collection 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_collection 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_collection. 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_collection 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.