Analyzes pod status, logs, and events to identify root causes and suggest solutions
AI agents call diagnose-pod 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 queries on Kubernetes cluster state—retrieving pod metadata, logs, and event data to provide analysis and recommendations. It has no side effects on the cluster. Even if misused by an AI agent, it cannot modify, delete, or execute operations; it merely reads and reports information. Blast radius is minimal as it cannot cause harm through cluster state changes.
From the tool's definition Tool 'diagnose-pod' analyzes pod status, logs, and events to identify root causes and suggest solutions. The verb 'analyzes' combined with 'identify' and 'suggest' indicates data retrieval and inspection only.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Analyzes pod status, logs, and events to identify root causes and suggest solutions. 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 diagnose-pod: 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.
diagnose-pod 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 diagnose-pod 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 diagnose-pod. 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.
diagnose-pod 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 →