Queries events for specific resources or namespaces and analyzes Warning events
AI agents call check-events 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 retrieves event data from Kubernetes resources or namespaces for diagnostic purposes. It performs read-only operations on existing cluster state (events) and provides analysis of Warning events without any side effects, modifications, or external command execution.
From the tool's definition Tool queries and analyzes events; description indicates 'Queries events' and 'analyzes' existing data without modification or deletion. No write, execute, or destructive operations are described.
Attacks that exploit this kind of access
Queries events for specific resources or namespaces and analyzes Warning events. 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 check-events: 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.
check-events 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-events 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-events. 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-events 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 →