Lists pods in Pending state (useful for detecting scheduling issues)
AI agents call k8s.get_pending_pods to retrieve information from K8s Mcp Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Kubernetes pod state information without modifying, executing, or deleting any resources. The read-only server design and the query-like nature of 'get' operations confirm this is a safe information-gathering capability. Severity is low because inspecting pod scheduling state poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_pending_pods' and description 'Lists pods in Pending state' indicate a retrieval operation. Server is explicitly described as 'read-only' with purpose to 'inspect app status' and 'view pod events' without requiring 'full kubectl access'.
Attacks that exploit this kind of access
Lists pods in Pending state (useful for detecting scheduling issues). It is categorised as a Read tool in the K8s Mcp Assistant MCP Server, which means it retrieves data without modifying state.
Register the K8s Mcp Assistant MCP server in PolicyLayer and add a rule for k8s.get_pending_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 Mcp Assistant. Nothing to install.
k8s.get_pending_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 k8s.get_pending_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 k8s.get_pending_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.
k8s.get_pending_pods is provided by the K8s Mcp Assistant MCP server (nicolasmosquerar/k8s-mcp-assistant). 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 →