delete_kubernetes_cluster
A destructive tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/delete-kubernetes-cluster.md
What delete_kubernetes_cluster does on Vultr MCP
AI agents call delete_kubernetes_cluster to permanently remove resources in Vultr MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_kubernetes_cluster is rated Critical
Deleting a Kubernetes cluster destroys all running containers, services, and data within that cluster (unless backed up externally), making this action irreversible and non-recoverable through the tool itself. This is the most severe category (Destructive > Execute > Write > Read).
From the tool's definition Tool name 'delete_kubernetes_cluster' indicates irreversible deletion of a Kubernetes cluster, which is a major cloud infrastructure resource. The 'delete_' prefix combined with 'cluster' scope confirms destructive capability.
Attacks that exploit this kind of access
The rule that runs delete_kubernetes_cluster safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_kubernetes_cluster, this is the rule to start with:
delete_kubernetes_cluster is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every delete_kubernetes_cluster call is checked against it from then on.
Questions about delete_kubernetes_cluster
delete_kubernetes_cluster is a destructive tool on the Vultr MCP server. It is categorised as a Destructive tool in the Vultr MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vultr MCP server in PolicyLayer and add a rule for delete_kubernetes_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 Vultr MCP. Nothing to install.
delete_kubernetes_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_kubernetes_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_kubernetes_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_kubernetes_cluster is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
Across the catalogue