AI agents call list_pods to retrieve information from K8s without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about Kubernetes pod resources. It performs no side effects, makes no changes to cluster state, and executes no commands. It is a straightforward read-only operation analogous to 'kubectl get pods', fitting the Read category for data retrieval without side effects. Severity is low as the blast radius of misuse is limited to information disclosure about existing pods.
From the tool's definition Tool description states 'List pods in a namespace or across all namespaces' — purely a query/retrieval operation with no modification, deletion, or execution.
Attacks that exploit this kind of access
List pods in a namespace or across all namespaces. It is categorised as a Read tool in the K8s MCP Server, which means it retrieves data without modifying state.
Register the K8s MCP server in PolicyLayer and add a rule for list_pods: 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. Nothing to install.
list_pods 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 list_pods 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 list_pods. 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.
list_pods is provided by the K8s MCP server (jingyanjiang/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 →