Analyzes pods in CrashLoop state by examining exit codes, logs, and events to find the root cause
AI agents call debug-crashloop to retrieve information from K8s Doctor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic inspection of Kubernetes resources (pod logs, exit codes, events) to understand failure states. It retrieves and queries information without creating, modifying, deleting, or executing operations against the cluster. The sibling tools (analyze-logs, check-events, check-resources, list-namespaces, list-pods) reinforce that this is a read-only diagnostic server.
From the tool's definition Tool 'debug-crashloop' analyzes pods by examining exit codes, logs, and events to find root cause. Descriptors 'examines', 'analyzes', and 'find the root cause' indicate data retrieval and diagnosis only, with no modification or execution of workloads.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Analyzes pods in CrashLoop state by examining exit codes, logs, and events to find the root cause. It is categorised as a Read tool in the K8s Doctor MCP MCP Server, which means it retrieves data without modifying state.
Register the K8s Doctor MCP server in PolicyLayer and add a rule for debug-crashloop: 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 Doctor MCP. Nothing to install.
debug-crashloop 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 debug-crashloop 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 debug-crashloop. 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.
debug-crashloop is provided by the K8s Doctor MCP server (ongjin/k8s-doctor-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 →