Create a pod in a Huawei CCE cluster
AI agents use create_pod to create or update resources in Huawei CCE MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huawei CCE MCP Server environment.
Creating a pod is a reversible write operation that modifies cluster state by instantiating a new workload. While not destructive (pods can be deleted), it is elevated from standard Write to high severity due to: (1) potential for resource exhaustion or denial-of-service if an agent creates numerous pods; (2) security implications if pods run with elevated privileges or malicious container images; (3) blast radius…
From the tool's definition Tool name 'create_pod' and description 'Create a pod in a Huawei CCE cluster' indicate creation of a new containerized workload in a production Kubernetes environment.
Attacks that exploit this kind of access
Create a pod in a Huawei CCE cluster. It is categorised as a Write tool in the Huawei CCE MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huawei CCE MCP Server MCP server in PolicyLayer and add a rule for create_pod: 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.
create_pod is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_pod 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 create_pod. 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.
create_pod 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.
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 →