Upgrade a Kubernetes cluster to a different version
AI agents invoke upgrade_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.
Upgrading a Kubernetes cluster is an active operation that triggers external infrastructure changes. It modifies the running state of the cluster by changing its version, which can affect all workloads running on it.
From the tool's definition Upgrade a Kubernetes cluster to a different version
Attacks that exploit this kind of access
Upgrade a Kubernetes cluster to a different version. 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.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for upgrade_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.
upgrade_kubernetes_cluster is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the upgrade_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 upgrade_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.
upgrade_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →