Delete a deployment
AI agents call delete_deployment to permanently remove resources in Kubernetes MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a deployment is a destructive operation that cannot be undone. It removes a production resource and all associated pods, potentially causing service outages. This is more severe than Execute or Write operations because the effects are irreversible. In a Kubernetes context where deployments manage critical workloads, misuse could have catastrophic impact on system availability and data integrity.
From the tool's definition Tool name 'delete_deployment' and description 'Delete a deployment' explicitly indicate irreversible deletion of Kubernetes deployment resources.
Attacks that exploit this kind of access
Delete a deployment. It is categorised as a Destructive tool in the Kubernetes MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for delete_deployment: 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 Kubernetes MCP Server. Nothing to install.
delete_deployment 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_deployment 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_deployment. 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_deployment is provided by the Kubernetes MCP Server MCP server (surukanti/k8s-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 →