New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

recycle_kubernetes_node

Recycle a node in a Kubernetes cluster

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/recycle-kubernetes-node.md

What recycle_kubernetes_node does on Linode MCP Server

AI agents invoke recycle_kubernetes_node to trigger actions in Linode 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 recycle_kubernetes_node is rated High

Recycling a Kubernetes node is an operational action that drains workloads from an existing node, deletes it, and provisions a replacement. This is an external infrastructure operation with significant blast radius (workloads may be disrupted, pods rescheduled or lost), making it Execute category.

From the tool's definition 'Recycle a node in a Kubernetes cluster' - recycling a node involves draining, deleting, and reprovisioning a Kubernetes node, which triggers external infrastructure operations

Questions about recycle_kubernetes_node

What does the recycle_kubernetes_node tool do? +

Recycle a node in a Kubernetes cluster. It is categorised as a Execute tool in the Linode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on recycle_kubernetes_node? +

Register the Linode MCP Server 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 Linode MCP Server. Nothing to install.

What risk level is recycle_kubernetes_node? +

recycle_kubernetes_node is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit recycle_kubernetes_node? +

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.

How do I block recycle_kubernetes_node completely? +

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.

What MCP server provides recycle_kubernetes_node? +

recycle_kubernetes_node is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Linode MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Linode MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.