remove_vms_from_kubernetes_cluster
Remove virtual machines from a Kubernetes cluster
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/remove-vms-from-kubernetes-cluster.md
What remove_vms_from_kubernetes_cluster does on CloudStack MCP Server
AI agents call remove_vms_from_kubernetes_cluster to permanently remove resources in CloudStack MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_vms_from_kubernetes_cluster is rated Critical
This tool performs an irreversible action—removing VMs from a Kubernetes cluster. While the VMs themselves may continue to exist, removing them from the cluster cannot be undone without manual intervention and may cause service disruption. This fits the Destructive category (actions that cannot be undone) rather than Execute, as the operation's effect is inherently destructive to cluster state.
From the tool's definition Tool name contains 'remove' and description states 'Remove virtual machines from a Kubernetes cluster'. Removing VMs from a cluster is an irreversible operation that disrupts infrastructure.
Attacks that exploit this kind of access
The rule that runs remove_vms_from_kubernetes_cluster safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_vms_from_kubernetes_cluster, this is the rule to start with:
remove_vms_from_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 CloudStack MCP Server, apply this rule, and every remove_vms_from_kubernetes_cluster call is checked against it from then on.
Questions about remove_vms_from_kubernetes_cluster
Remove virtual machines from a Kubernetes cluster. It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for remove_vms_from_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 CloudStack MCP Server. Nothing to install.
remove_vms_from_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 remove_vms_from_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 remove_vms_from_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.
remove_vms_from_kubernetes_cluster is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CloudStack MCP Server, and thousands of servers like it.
Across the catalogue