Drain a Kubernetes node by evicting all non-daemonset pods.
AI agents invoke ralph_hero__sre__drain to trigger actions in Ralph Hero. 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.
Draining a Kubernetes node forcibly evicts all running pods (except daemonsets), causing service disruption and potential data loss for stateful workloads. This is an irreversible operational action with a massive blast radius — it can take down production services.
From the tool's definition Drain a Kubernetes node by evicting all non-daemonset pods
Attacks that exploit this kind of access
Drain a Kubernetes node by evicting all non-daemonset pods. It is categorised as a Execute tool in the Ralph Hero MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__sre__drain: 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 Ralph Hero. Nothing to install.
ralph_hero__sre__drain 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 ralph_hero__sre__drain 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 ralph_hero__sre__drain. 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.
ralph_hero__sre__drain is provided by the Ralph Hero MCP server (ralph-hero-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →