start_kubernetes_cluster · CloudStack MCP Server MCP

WHAT IT DOES

What start_kubernetes_cluster does on CloudStack MCP Server

AI agents invoke start_kubernetes_cluster to trigger actions in CloudStack MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_kubernetes_cluster needs a policy

This tool executes a command that starts a Kubernetes cluster—an infrastructure operation with significant side effects. It is not merely reading data (Read), nor is it a simple data modification (Write). Starting a cluster provisions compute resources, configures networking, and initializes services, making it an Execute-category tool.

From the tool's definition Tool name 'start_kubernetes_cluster' indicates execution of a cluster startup operation. Description 'Start a Kubernetes cluster' confirms this triggers an external orchestration operation whose effects depend on cluster configuration arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_kubernetes_cluster Rate-limited

start_kubernetes_cluster stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_kubernetes_cluster": {
      "limits": [
        {
          "counter": "start_kubernetes_cluster_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 start_kubernetes_cluster

What does the start_kubernetes_cluster tool do? +

Start a Kubernetes cluster. It is categorised as a Execute tool in the CloudStack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_kubernetes_cluster? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for start_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 start_kubernetes_cluster? +

start_kubernetes_cluster is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_kubernetes_cluster? +

Yes. Add a rate_limit block to the start_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 start_kubernetes_cluster completely? +

Set action: deny in the PolicyLayer policy for start_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 start_kubernetes_cluster? +

start_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.