get_pod_by_name_and_namespace

Get a specific pod in a Huawei CCE cluster by name and namespace

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

What get_pod_by_name_and_namespace does on Huawei CCE MCP Server

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

Why get_pod_by_name_and_namespace needs a policy

This tool retrieves information about a pod given its name and namespace. It performs a query operation against the Kubernetes cluster state with no capability to create, modify, delete, or execute actions. The blast radius of misuse is minimal—the worst outcome would be information disclosure about pod configuration or status within an already-accessible namespace.

From the tool's definition Tool name includes 'get_' prefix and description states 'Get a specific pod', indicating retrieval of existing data without modification. No side effects or state changes occur.

Questions about get_pod_by_name_and_namespace

What does the get_pod_by_name_and_namespace tool do? +

Get a specific pod in a Huawei CCE cluster by name and namespace. It is categorised as a Read tool in the Huawei CCE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pod_by_name_and_namespace? +

Register the Huawei CCE MCP Server MCP server in PolicyLayer and add a rule for get_pod_by_name_and_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 get_pod_by_name_and_namespace? +

get_pod_by_name_and_namespace is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pod_by_name_and_namespace? +

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

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

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