cluster_get_events
AI agents call cluster_get_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 cluster events for monitoring/auditing purposes without modifying infrastructure. Event retrieval is a read operation with no side effects. Severity is low because event logs contain operational information but not sensitive credentials or system-critical data.
From the tool's definition Tool name 'cluster_get_events' indicates retrieval of event data from Kubernetes clusters. The 'get' prefix and 'events' suffix are consistent with read-only query operations.
Attacks that exploit this kind of access
cluster_get_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 cluster_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 GreenNode MCP Server. Nothing to install.
cluster_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 cluster_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 cluster_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.
cluster_get_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 →