Describe details of a Kubernetes pod
AI agents call describe-pod to retrieve information from Kubernetes MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The describe-pod tool retrieves and displays information about a Kubernetes pod's current state, configuration, and metadata. This is a read-only operation with no side effects on cluster state. While Kubernetes pods can contain sensitive information (environment variables, secrets references), the risk is mitigated by existing RBAC controls and audit logging. Blast radius is limited to information disclosure only.
From the tool's definition Tool name 'describe-pod' and description 'Describe details of a Kubernetes pod' indicate retrieval of pod metadata and status information without modification.
Attacks that exploit this kind of access
Describe details of a Kubernetes pod. It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for describe-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 Kubernetes MCP Server. Nothing to install.
describe-pod 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 describe-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 describe-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.
describe-pod is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-mcp). 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 →