k8s_drain_node

THE RISK

Critical Risk

Why k8s_drain_node needs a policy

Draining a node forcibly evicts all running pods from that node. This is a disruptive, largely irreversible operation in the moment — evicted pods may be rescheduled elsewhere but workloads are interrupted, stateful pods may lose in-flight state, and PodDisruptionBudgets may be bypassed. The blast radius is high as it can take down all workloads on a node simultaneously, potentially affecting production services.

From the tool's definition Drain a node by evicting all pods, preparing it for maintenance

Documented attack patterns abuse exactly the kind of access k8s_drain_node gives an agent:

POLICY

How to control k8s_drain_node

PolicyLayer is an MCP gateway — it sits between your AI agents and Multi Cluster Kubernetes MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for k8s_drain_node:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "k8s_drain_node"
  ]
}

k8s_drain_node disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Multi Cluster Kubernetes MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Multi Cluster Kubernetes MCP Server tools

Destructive k8s_delete_ns Delete a Kubernetes namespace and all resources within it. Destructive k8s_delete_resource Delete a Kubernetes resource. Supports all common resource types Execute k8s_pod_exec Execute a command inside a running container. Supports quoted arguments Execute k8s_rollout_restart Trigger a rolling restart of a deployment, daemonset, or statefulset. Execute k8s_run_pod Create and run a pod with the specified container image. Execute k8s_scale_resource Scale a deployment, statefulset, or replicaset to the specified number of replicas. Execute k8s_rollout_pause Pause an in-progress rollout for a deployment, daemonset, or statefulset. Execute k8s_rollout_undo Roll back a deployment, daemonset, or statefulset to a previous revision.

All 57 Multi Cluster Kubernetes MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Multi Cluster Kubernetes MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about k8s_drain_node

What does the k8s_drain_node tool do? +

Drain a node by evicting all pods, preparing it for maintenance. It is categorised as a Destructive tool in the Multi Cluster Kubernetes MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on k8s_drain_node? +

Register the Multi Cluster Kubernetes MCP Server MCP server in PolicyLayer and add a rule for k8s_drain_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 Multi Cluster Kubernetes MCP Server. Nothing to install.

What risk level is k8s_drain_node? +

k8s_drain_node is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit k8s_drain_node? +

Yes. Add a rate_limit block to the k8s_drain_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 k8s_drain_node completely? +

Set action: deny in the PolicyLayer policy for k8s_drain_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 k8s_drain_node? +

k8s_drain_node is provided by the Multi Cluster Kubernetes MCP Server MCP server (razvanmacovei/k8s-multicluster-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Multi Cluster Kubernetes MCP Server tool call.

Start from Multi Cluster Kubernetes MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →