Find problematic pods
AI agents call k8s.listProblemPods 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.
This is a read-only operation that retrieves and reports pod status information. It queries the Kubernetes cluster to identify problematic pods but does not modify, execute, or delete anything. The action is informational for monitoring and troubleshooting purposes. Confidence is high due to clear read-only semantics in both name and context of a monitoring/troubleshooting server.
From the tool's definition Tool name 'listProblemPods' and description 'Find problematic pods' indicate data retrieval and querying of pod status with no modification or execution capabilities.
Attacks that exploit this kind of access
Find problematic pods. 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 k8s.listProblemPods: 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.
k8s.listProblemPods 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 k8s.listProblemPods 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 k8s.listProblemPods. 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.
k8s.listProblemPods is provided by the Kubernetes MCP Server MCP server (kishanrao92/infra-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 →