Get a specific cluster by ID
AI agents call get_cluster_by_id to retrieve information from Huawei CCE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about a Kubernetes cluster identified by ID. It performs a query operation without modifying, deleting, or executing anything. The blast radius of misuse is minimal—an attacker gains visibility into cluster metadata but cannot change infrastructure or access workload data beyond what the cluster object exposes.
From the tool's definition Tool name 'get_cluster_by_id' and description 'Get a specific cluster by ID' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a specific cluster by ID. It is categorised as a Read tool in the Huawei CCE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Huawei CCE MCP Server MCP server in PolicyLayer and add a rule for get_cluster_by_id: 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.
get_cluster_by_id is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_cluster_by_id 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 get_cluster_by_id. 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.
get_cluster_by_id 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 →