Delete an OKE cluster.
AI agents call delete_cluster to permanently remove resources in OCI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a Kubernetes cluster is a destructive action that cannot be undone. It terminates all containerized workloads, removes persistent storage configurations, and invalidates compute resources. The blast radius is critical: any agent invoking this without proper confirmation could catastrophically disrupt production systems.
From the tool's definition Tool name and description: 'delete_cluster' / 'Delete an OKE cluster.' The verb 'delete' and the action of removing a Kubernetes cluster are irreversible operations that destroy infrastructure, data, and services.
Attacks that exploit this kind of access
Delete an OKE cluster. It is categorised as a Destructive tool in the OCI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OCI MCP Server 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 OCI MCP Server. 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 OCI MCP Server MCP server (sarthak-pansare/oci-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →