Delete a pod.
AI agents call delete_pod to permanently remove resources in K8s — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a pod terminates the running container(s) and workload associated with it. While Kubernetes may automatically restart the pod if it is managed by a controller (Deployment, StatefulSet, etc.), the deletion action itself is irreversible—the pod object is removed from the cluster. This falls squarely into the Destructive category.
From the tool's definition Tool name is 'delete_pod' with description 'Delete a pod.' The verb 'Delete' combined with the lack of any reversible mechanism or undo capability indicates irreversible removal of a Kubernetes pod resource.
Attacks that exploit this kind of access
Delete a pod. It is categorised as a Destructive tool in the K8s MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the K8s MCP server in PolicyLayer and add a rule for 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 K8s. Nothing to install.
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 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 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.
delete_pod is provided by the K8s MCP server (jingyanjiang/k8s-mcp). 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 →