Critical Risk →

ibmcloud_ks_cluster_delete

Delete a Kubernetes cluster

Part of the Ibmcloud MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

ibmcloud-mcp-server Destructive Risk 4/5

AI agents may call ibmcloud_ks_cluster_delete to permanently remove or destroy resources in Ibmcloud. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call ibmcloud_ks_cluster_delete in a loop, permanently destroying resources in Ibmcloud. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-expertvagabond-ibmcloud.yaml
tools:
  ibmcloud_ks_cluster_delete:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Ibmcloud policy for all 88 tools.

Tool Name ibmcloud_ks_cluster_delete
Category Destructive
MCP Server Ibmcloud MCP Server
Risk Level Critical

View all 88 tools →

Agents calling destructive-class tools like ibmcloud_ks_cluster_delete have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

ibmcloud_ks_cluster_delete is one of the critical-risk operations in Ibmcloud. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the ibmcloud_ks_cluster_delete tool do? +

Delete a Kubernetes cluster. It is categorised as a Destructive tool in the Ibmcloud 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 ibmcloud_ks_cluster_delete? +

Add a rule in your Intercept YAML policy under the tools section for ibmcloud_ks_cluster_delete. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ibmcloud MCP server.

What risk level is ibmcloud_ks_cluster_delete? +

ibmcloud_ks_cluster_delete 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 ibmcloud_ks_cluster_delete? +

Yes. Add a rate_limit block to the ibmcloud_ks_cluster_delete rule in your Intercept 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 ibmcloud_ks_cluster_delete completely? +

Set action: deny in the Intercept policy for ibmcloud_ks_cluster_delete. 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 ibmcloud_ks_cluster_delete? +

ibmcloud_ks_cluster_delete is provided by the Ibmcloud MCP server (ibmcloud-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ibmcloud

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.