add_vms_to_kubernetes_cluster · CloudStack MCP Server MCP

WHAT IT DOES

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 IT NEEDS A POLICY

Why add_vms_to_kubernetes_cluster needs a policy

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

Recommended rule Ready

Verdict

add_vms_to_kubernetes_cluster Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_vms_to_kubernetes_cluster": {
      "limits": [
        {
          "counter": "add_vms_to_kubernetes_cluster_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about add_vms_to_kubernetes_cluster

What does the add_vms_to_kubernetes_cluster tool do? +

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.

How do I enforce a policy on add_vms_to_kubernetes_cluster? +

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.

What risk level is add_vms_to_kubernetes_cluster? +

add_vms_to_kubernetes_cluster is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_vms_to_kubernetes_cluster? +

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.

How do I block add_vms_to_kubernetes_cluster completely? +

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.

What MCP server provides add_vms_to_kubernetes_cluster? +

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.