Check pod status and identify issues
AI agents call check_pod_status 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 tool performs observability and diagnostics by retrieving pod status information. It does not create, modify, delete, or execute operations; it only reads and reports current cluster state. The blast radius of misuse is minimal — an attacker could only gain visibility into pod health, not alter infrastructure or cause harm.
From the tool's definition Tool name is 'check_pod_status' and description states 'Check pod status and identify issues' — both indicate a read-only query operation that retrieves pod state information without modifying cluster state.
Attacks that exploit this kind of access
Check pod status and identify issues. 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 check_pod_status: 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.
check_pod_status 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 check_pod_status 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 check_pod_status. 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.
check_pod_status is provided by the Kubernetes MCP Server MCP server (vivekbala/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 →