recycle_kubernetes_node
A execute tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/recycle-kubernetes-node.md
What recycle_kubernetes_node does on Vultr MCP
AI agents invoke recycle_kubernetes_node 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 recycle_kubernetes_node is rated High
Recycling a Kubernetes node involves draining, deleting, and reprovisioning the node, which is a significant infrastructure operation. It is not purely destructive (data is not permanently lost) but it does execute an external operation with potentially high blast radius (workloads disrupted, node temporarily unavailable). The description is empty, lowering confidence.
From the tool's definition Tool name: 'recycle_kubernetes_node' — 'recycle' implies restarting/replacing a Kubernetes node, which triggers an external infrastructure operation.
Attacks that exploit this kind of access
The rule that runs recycle_kubernetes_node 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 recycle_kubernetes_node, this is the rule to start with:
recycle_kubernetes_node 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 recycle_kubernetes_node call is checked against it from then on.
Questions about recycle_kubernetes_node
recycle_kubernetes_node 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 recycle_kubernetes_node: 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.
recycle_kubernetes_node 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 recycle_kubernetes_node 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 recycle_kubernetes_node. 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.
recycle_kubernetes_node 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