This record as markdown: /tools/com-googleapis-container-mcp/delete-k8s-resource.md
What delete_k8s_resource does on Mcp
AI agents call delete_k8s_resource to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Required. The name of the resource to delete. |
dryRun | boolean | — | Optional. If true, run in dry-run mode. |
parent | string | Yes | Required. The cluster, which owns this collection of resources. Format: projects/{project}/locations/{location}/clusters/{cluster} |
cascade | string | — | Optional. The cascading deletion policy to use. If not specified, 'background' is used. Valid values are 'background', 'foreground', and 'orphan'. |
namespace | string | — | Optional. The namespace of the resource. If not specified, "default" is used. |
resourceType | string | Yes | Required. The type of resource to delete. Kubernetes resource/kind name in singular form, lower case. e.g. "pod", "deployment", "service". |
Parameters from the server's own tool schema.
Why delete_k8s_resource is rated Critical
This tool permanently removes Kubernetes resources (pods, deployments, services, etc.) from a cluster with no built-in undo mechanism. Deletion of cluster resources cannot be reversed and can cause immediate service outages, data loss, and infrastructure failure. An AI agent with access could maliciously or accidentally destroy critical production workloads. This is the most severe category applicable.
From the tool's definition Tool name is 'delete_k8s_resource' and description explicitly states 'Deletes a Kubernetes resource from a cluster.
Attacks that exploit this kind of access
The rule that runs delete_k8s_resource safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_k8s_resource, this is the rule to start with:
delete_k8s_resource is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every delete_k8s_resource call is checked against it from then on.
Questions about delete_k8s_resource
Deletes a Kubernetes resource from a cluster. This is similar to running kubectl delete. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_k8s_resource accepts 6 parameters: name, dryRun, parent, cascade, namespace, resourceType. Required: name, parent, resourceType. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for delete_k8s_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 Mcp. Nothing to install.
delete_k8s_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_k8s_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_k8s_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_k8s_resource is provided by the MCP server (https://container.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue