Find all CrashLoopBackOff pods across ALL namespaces
AI agents call get_crashlooping_pods to retrieve information from Kubernetes + Prometheus SRE 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 a read-only query of Kubernetes cluster state (specifically, pods in CrashLoopBackOff status). It retrieves diagnostic information about failing pods but has no side effects—it neither modifies pod configurations, executes commands within pods, nor deletes resources. The blast radius of misuse is minimal (information disclosure of pod names and status), making this a low-severity read operation.
From the tool's definition Tool name 'get_crashlooping_pods' and description 'Find all CrashLoopBackOff pods across ALL namespaces' indicate a retrieval operation that queries pod status information without modifying, executing, or deleting any resources.
Attacks that exploit this kind of access
Find all CrashLoopBackOff pods across ALL namespaces. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for get_crashlooping_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 Kubernetes + Prometheus SRE MCP Server. Nothing to install.
get_crashlooping_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 get_crashlooping_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 get_crashlooping_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.
get_crashlooping_pods is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-mcp-server). 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 →