View Kubernetes events. Filter by namespace and field selectors (e.g., type=Warning).
AI agents call k8s_events to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries Kubernetes event logs with filtering options. No action in the description suggests creation, modification, deletion, or execution of operations. This is a read-only monitoring and intelligence gathering capability, which carries minimal risk even if misused by an AI agent, as it only exposes visibility into existing events without affecting cluster state or workloads.
From the tool's definition Tool name 'k8s_events' and description 'View Kubernetes events. Filter by namespace and field selectors' indicate retrieval and querying of event data with no modification or deletion capability.
Attacks that exploit this kind of access
View Kubernetes events. Filter by namespace and field selectors (e.g., type=Warning). It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus 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 RedisNexus. 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 RedisNexus MCP server (rajkumar-madhu/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 →