add_vms_to_kubernetes_cluster
Add virtual machines to an existing Kubernetes cluster
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/add-vms-to-kubernetes-cluster.md
What add_vms_to_kubernetes_cluster does on CloudStack MCP Server
AI agents use add_vms_to_kubernetes_cluster to create or update resources in CloudStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.
Why add_vms_to_kubernetes_cluster is rated Medium
This tool modifies cluster membership by adding VMs, which is a Write-class operation (creates or modifies data reversibly). Severity is medium because misconfiguration could degrade cluster stability or consume resources, but the operation is not destructive and can be undone.
From the tool's definition Tool name and description indicate 'Add virtual machines' to a cluster, which is a create/modify operation that adds resources to an existing infrastructure component. The action is reversible (VMs can be removed from clusters).
Attacks that exploit this kind of access
The rule that runs add_vms_to_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 add_vms_to_kubernetes_cluster, this is the rule to start with:
add_vms_to_kubernetes_cluster stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every add_vms_to_kubernetes_cluster call is checked against it from then on.
Questions about add_vms_to_kubernetes_cluster
Add virtual machines to an existing Kubernetes cluster. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for add_vms_to_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.
add_vms_to_kubernetes_cluster is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_vms_to_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 add_vms_to_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.
add_vms_to_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.
This server
Across the catalogue