upgrade_kubernetes_cluster
A execute tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/upgrade-kubernetes-cluster.md
What upgrade_kubernetes_cluster does on Vultr MCP
AI agents invoke upgrade_kubernetes_cluster to trigger actions in Vultr MCP. 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 upgrade_kubernetes_cluster is rated High
Upgrading a Kubernetes cluster triggers an external operational change to live infrastructure (control plane and node pool version changes). This is an Execute-level action with high blast radius since a failed or unintended upgrade can disrupt running workloads across the entire cluster. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'upgrade_kubernetes_cluster' — description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs upgrade_kubernetes_cluster safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upgrade_kubernetes_cluster, this is the rule to start with:
upgrade_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every upgrade_kubernetes_cluster call is checked against it from then on.
Questions about upgrade_kubernetes_cluster
upgrade_kubernetes_cluster is a execute tool on the Vultr MCP server. It is categorised as a Execute tool in the Vultr MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vultr 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 Vultr MCP. 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 Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
Across the catalogue