get_k8s_events
AI agents call get_k8s_events to retrieve information from GreenNode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Kubernetes cluster events for monitoring/observability purposes. Reading event logs does not modify infrastructure state, execute code, or cause destructive operations. The empty description reduces confidence slightly, but the naming convention and context (alongside cluster management tools) clearly indicate a data retrieval function.
From the tool's definition Tool name 'get_k8s_events' indicates retrieval of Kubernetes events; sibling tools like 'cluster_get' and 'cluster_get_events' in this context confirm Read-pattern behavior. The 'get_' prefix strongly suggests a query operation without side effects.
Attacks that exploit this kind of access
get_k8s_events. It is categorised as a Read tool in the GreenNode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for get_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 GreenNode MCP Server. Nothing to install.
get_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 get_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 get_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.
get_k8s_events is provided by the GreenNode MCP Server MCP server (vngcloud/greennode-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 →