scale_kubernetes_node_pool
A execute tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/scale-kubernetes-node-pool.md
What scale_kubernetes_node_pool does on Vultr MCP
AI agents invoke scale_kubernetes_node_pool 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 scale_kubernetes_node_pool is rated High
Scaling a Kubernetes node pool is an infrastructure operation that triggers external effects (cluster resource allocation changes, potential service disruptions, cost implications). While not destructive (scaling can be reversed), it is an Execute action because it runs infrastructure commands whose effects depend on arguments (target pool, node count, etc.).
From the tool's definition Tool name 'scale_kubernetes_node_pool' indicates it performs a resource scaling operation on a Kubernetes cluster node pool. The verb 'scale' implies execution of a command that modifies the state of infrastructure.
Attacks that exploit this kind of access
The rule that runs scale_kubernetes_node_pool 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 scale_kubernetes_node_pool, this is the rule to start with:
scale_kubernetes_node_pool 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 scale_kubernetes_node_pool call is checked against it from then on.
Questions about scale_kubernetes_node_pool
scale_kubernetes_node_pool 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 scale_kubernetes_node_pool: 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.
scale_kubernetes_node_pool 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 scale_kubernetes_node_pool 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 scale_kubernetes_node_pool. 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.
scale_kubernetes_node_pool 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