get_k8s_events
AI agents call get_k8s_events to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and 'events' noun pattern indicate this retrieves or queries Kubernetes event data without modifying state. No evidence of data creation, deletion, execution, or financial operations. Classified as Read with low severity due to standard observability operations on event logs.
From the tool's definition Tool name 'get_k8s_events' indicates retrieval of Kubernetes events; 'get_' prefix strongly suggests a read-only query operation with no side effects. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
get_k8s_events. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.