scale_kubernetes_cluster

What scale_kubernetes_cluster does on CloudStack MCP Server

AI agents invoke scale_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 scale_kubernetes_cluster is rated High

This tool triggers external infrastructure operations (Kubernetes cluster scaling) whose consequences are determined by the arguments passed. It is not a simple Read (no query-only semantics), Write (reversible data modification), or Destructive (permanent deletion). While scaling can be reversed, the immediate action is an Execute-category operation that directly modifies a live system.

From the tool's definition Tool name 'scale_kubernetes_cluster' and description 'Scale a Kubernetes cluster up or down' indicate execution of infrastructure operations whose effects depend on the scaling parameters provided (direction and magnitude).

The rule that runs scale_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 scale_kubernetes_cluster, this is the rule to start with:

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

Questions about scale_kubernetes_cluster