Retrieves recent cluster events for troubleshooting
AI agents call k8s.get_events to retrieve information from K8s Mcp Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Kubernetes cluster events without creating, modifying, deleting, or executing any operations. It is a passive information-gathering tool appropriate for troubleshooting and monitoring. The read-only server designation and the retrieval-focused description confirm it falls squarely into the Read category with minimal security risk.
From the tool's definition Tool name 'get_events' and description 'Retrieves recent cluster events for troubleshooting' indicate a data retrieval operation. Server is explicitly described as 'read-only' and the tool performs no modifications or side effects.
Attacks that exploit this kind of access
Retrieves recent cluster events for troubleshooting. It is categorised as a Read tool in the K8s Mcp Assistant MCP Server, which means it retrieves data without modifying state.
Register the K8s Mcp Assistant MCP server in PolicyLayer and add a rule for k8s.get_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 Mcp Assistant. Nothing to install.
k8s.get_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 k8s.get_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 k8s.get_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.
k8s.get_events is provided by the K8s Mcp Assistant MCP server (nicolasmosquerar/k8s-mcp-assistant). 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 →