k8s_delete_namespace

Delete a namespace (WARNING: This will delete all resources in the namespace)

Server Kubernetes MCP Server mjrestivo16/mcp-kubernetes
Category Destructive
Risk class Critical
Parameters 00 required

What k8s_delete_namespace does on Kubernetes MCP Server

AI agents call k8s_delete_namespace 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.

Why k8s_delete_namespace needs a policy

Deleting a namespace is an irreversible destructive action that cascades to remove all pods, services, deployments, configmaps, secrets, and other resources within it. This represents maximum blast radius in a Kubernetes cluster, potentially causing complete loss of application infrastructure and data. The warning in the description confirms the destructive nature.

From the tool's definition Tool name explicitly states 'delete_namespace' and description warns 'This will delete all resources in the namespace' - irreversible deletion of namespace and all contained resources.

Questions about k8s_delete_namespace

What does the k8s_delete_namespace tool do? +

Delete a namespace (WARNING: This will delete all resources in the namespace). 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.

How do I enforce a policy on k8s_delete_namespace? +

Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for k8s_delete_namespace: 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.

What risk level is k8s_delete_namespace? +

k8s_delete_namespace is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit k8s_delete_namespace? +

Yes. Add a rate_limit block to the k8s_delete_namespace 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.

How do I block k8s_delete_namespace completely? +

Set action: deny in the PolicyLayer policy for k8s_delete_namespace. 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.

What MCP server provides k8s_delete_namespace? +

k8s_delete_namespace is provided by the Kubernetes MCP Server MCP server (mjrestivo16/mcp-kubernetes). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.