delete_pods_by_namespace

Delete all pods in a namespace in a Huawei CCE cluster

Server Huawei CCE MCP Server tehilathestudent/try-cce-gitlab
Category Destructive
Risk class Critical
Parameters 00 required

What delete_pods_by_namespace does on Huawei CCE MCP Server

AI agents call delete_pods_by_namespace to permanently remove resources in Huawei CCE MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_pods_by_namespace needs a policy

This tool permanently removes all pods within a namespace without apparent undo capability. Pods are the atomic unit of container orchestration; deleting all pods in a namespace causes immediate workload loss, service disruption, and data loss if pods are stateless or lack persistent storage. The blast radius is severe: an agent error or prompt injection could eliminate entire application environments.

From the tool's definition Tool name explicitly states 'delete' and description confirms it 'Delete all pods in a namespace' - irreversible removal of containerized workloads at scale.

Questions about delete_pods_by_namespace

What does the delete_pods_by_namespace tool do? +

Delete all pods in a namespace in a Huawei CCE cluster. It is categorised as a Destructive tool in the Huawei CCE 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 delete_pods_by_namespace? +

Register the Huawei CCE MCP Server MCP server in PolicyLayer and add a rule for delete_pods_by_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 Huawei CCE MCP Server. Nothing to install.

What risk level is delete_pods_by_namespace? +

delete_pods_by_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 delete_pods_by_namespace? +

Yes. Add a rate_limit block to the delete_pods_by_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 delete_pods_by_namespace completely? +

Set action: deny in the PolicyLayer policy for delete_pods_by_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 delete_pods_by_namespace? +

delete_pods_by_namespace is provided by the Huawei CCE MCP Server MCP server (tehilathestudent/try-cce-gitlab). 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.