delete_namespace

Delete 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_namespace does on Huawei CCE MCP Server

AI agents call delete_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_namespace needs a policy

Deleting a namespace destroys data and Kubernetes resources irreversibly and cannot be undone. This is a destructive action with significant blast radius if triggered by an AI agent against the wrong namespace, potentially affecting multiple pods and services. While not as critical as deleting an entire cluster, namespace deletion is a high-severity destructive operation that warrants careful access control.

From the tool's definition Tool name is 'delete_namespace' and description states 'Delete a namespace in a Huawei CCE cluster'. Deletion of a namespace is an irreversible operation that removes the namespace and typically all resources contained within it.

Questions about delete_namespace

What does the delete_namespace tool do? +

Delete 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_namespace? +

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

What risk level is delete_namespace? +

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 delete_namespace? +

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

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

delete_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.

// THE FULL RECORD

delete_namespace is one line of Huawei CCE MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.