Delete a Kubernetes resource by type and name.
AI agents call delete_resource 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 Kubernetes resources (pods, deployments, services, etc.) is irreversible and has immediate blast radius effects: workloads stop running, data may be lost, services become unavailable, and clusters destabilize. An AI agent with unsupervised access to this tool could terminate critical production workloads. This is the most severe category applicable and warrants critical severity.
From the tool's definition Tool name 'delete_resource' and description 'Delete a Kubernetes resource by type and name' explicitly indicate irreversible deletion of Kubernetes resources. This is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a Kubernetes resource by type and name. 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_resource: 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_resource 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_resource 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_resource. 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_resource 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 →