AI agents call describe_pod to retrieve information from K8s MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and inspects pod metadata and status information, which is a non-destructive read operation with no side effects. It does not create, modify, execute code, delete, or trigger any external operations. The minimal blast radius of returning informational data about existing resources justifies a 'low' severity classification.
From the tool's definition Tool name 'describe_pod' and description 'Return detailed pod object as JSON' indicate a read-only query operation that retrieves and returns information about a pod without modifying, executing, or deleting any resources.
Attacks that exploit this kind of access
Return detailed pod object as JSON. It is categorised as a Read tool in the K8s MCP MCP Server, which means it retrieves data without modifying state.
Register the K8s 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 K8s MCP. 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 K8s MCP server (rahul007-bit/k8s-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 →