AI agents call get_pod_status 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.
The tool retrieves pod status, a read-only operation that queries Kubernetes cluster state. No side effects or modifications occur. Even if an AI agent uses this tool incorrectly, it cannot damage resources or create obligations—it only returns information. Low severity reflects minimal blast radius from misuse.
From the tool's definition Tool name 'get_pod_status' indicates retrieval of pod status information. No description provided, but naming convention and context within Kubernetes management tools (alongside destructive tools like delete_pod, delete_resource) strongly suggests this is a…
Attacks that exploit this kind of access
get_pod_status. 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 get_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 K8s MCP. Nothing to install.
get_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 get_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 get_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.
get_pod_status 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 →