Delete a single named pod in a Kubernetes namespace.
AI agents call ralph_hero__sre__delete_pod to permanently remove resources in Ralph Hero — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a Kubernetes pod terminates the container and its workload, which cannot be undone without redeployment. This is a destructive action with significant blast radius in production environments—loss of service availability, data loss if not replicated, and disruption of dependent systems.
From the tool's definition Tool name explicitly states 'delete_pod' and description confirms 'Delete a single named pod in a Kubernetes namespace.' The verb 'Delete' combined with pod termination is an irreversible operation.
Attacks that exploit this kind of access
Delete a single named pod in a Kubernetes namespace. It is categorised as a Destructive tool in the Ralph Hero MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ralph Hero MCP server in PolicyLayer and add a rule for ralph_hero__sre__delete_pod: 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__delete_pod is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ralph_hero__sre__delete_pod 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__delete_pod. 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__delete_pod 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 →