Get events for a namespace or pod
AI agents call k8s_events to retrieve information from MCP Container Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists events from a Kubernetes cluster—a read-only operation with no side effects. Kubernetes events are logs of cluster activities and are safe to query. The context of sibling tools (azure_availability, azure_metrics, azure_traces, compose_logs, compose_ps) all being observability/monitoring tools reinforces this classification. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'k8s_events' and description 'Get events for a namespace or pod' indicate a retrieval operation that queries Kubernetes event data without modifying state.
Attacks that exploit this kind of access
Get events for a namespace or pod. It is categorised as a Read tool in the MCP Container Tools MCP Server, which means it retrieves data without modifying state.
Register the MCP Container Tools MCP server in PolicyLayer and add a rule for k8s_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 MCP Container Tools. Nothing to install.
k8s_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_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_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_events is provided by the MCP Container Tools MCP server (simseksem/mcp-container-tools). 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 →