删除指定命名空间中的OceanBase集群 Args: cluster_name: 要删除的集群名称 namespace: 要从中删除集群的命名空间
AI agents call delete_cluster 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 deletes an entire OceanBase database cluster, which is an irreversible destruction of infrastructure and all associated data. This is the most severe category (Destructive > Execute > Write > Read) due to the inability to undo the operation and the massive blast radius of losing a complete cluster and its data.
From the tool's definition Tool name is 'delete_cluster' and description states '删除指定命名空间中的OceanBase集群' (delete an OceanBase cluster from the specified namespace). The parameters are cluster_name and namespace, confirming the action removes a cluster irreversibly.
Documented attack patterns abuse exactly the kind of access delete_cluster 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_cluster:
{
"version": "1",
"default": "deny",
"hide": [
"delete_cluster"
]
} delete_cluster 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.
删除指定命名空间中的OceanBase集群 Args: cluster_name: 要删除的集群名称 namespace: 要从中删除集群的命名空间. 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_cluster: 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_cluster 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_cluster 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_cluster. 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_cluster 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.