list_k8s_events
Retrieves events from a Kubernetes cluster. This is similar to running kubectl events.
This record as markdown: /tools/com-googleapis-container-mcp/list-k8s-events.md
What list_k8s_events does on Mcp
AI agents call list_k8s_events to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Optional. The name of the resource to retrieve events for. |
limit | string | — | Optional. The maximum number of events to return. If not specified, 500 is used. |
parent | string | Yes | Required. The parent cluster. Format: projects/{project}/locations/{location}/clusters/{cluster} |
namespace | string | — | Optional. The namespace of the resource. If not specified and all_namespaces is false, "default" is used. |
resourceType | string | — | Optional. The type of the resource to retrieve events for. |
allNamespaces | boolean | — | Optional. If true, retrieve events from all namespaces. |
Parameters from the server's own tool schema.
Why list_k8s_events is rated Low
The tool retrieves and queries existing event data from Kubernetes resources without creating, modifying, deleting, or executing any operations. It is purely informational in nature, consistent with kubectl's events command which only displays audit trails and cluster events.
From the tool's definition Tool description states it 'Retrieves events from a Kubernetes cluster' and is 'similar to running `kubectl events`', which is a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_k8s_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_k8s_events, this is the rule to start with:
list_k8s_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_k8s_events call is checked against it from then on.
Questions about list_k8s_events
Retrieves events from a Kubernetes cluster. This is similar to running kubectl events. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_k8s_events accepts 6 parameters: name, limit, parent, namespace, resourceType, allNamespaces. Required: parent. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for list_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. Nothing to install.
list_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 list_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 list_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.
list_k8s_events is provided by the MCP server (https://container.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue