Low Risk

lookup_events

lookup_events

How to control lookup_events ↓

What lookup_events does on Amazon EKS MCP Server

AI agents call lookup_events to retrieve information from Amazon EKS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why lookup_events needs a policy

The name 'lookup_events' suggests a read-only query operation that retrieves event information without side effects. The empty description reduces confidence slightly, but the semantic meaning of 'lookup' strongly indicates a retrieval operation. This aligns with the Read category (search, list, get, fetch). Even in an EKS context, event lookups typically retrieve audit/system logs without modification.

From the tool's definition Tool name is 'lookup_events' which indicates querying/retrieving event data. No description provided to confirm destructive, write, or execute capabilities.

Documented attack patterns abuse exactly the kind of access lookup_events gives an agent:

How to control lookup_events

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lookup_events:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lookup_events": {}
  }
}

lookup_events is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon EKS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about lookup_events

What does the lookup_events tool do? +

lookup_events. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lookup_events? +

Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for lookup_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 Amazon EKS MCP Server. Nothing to install.

What risk level is lookup_events? +

lookup_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lookup_events? +

Yes. Add a rate_limit block to the lookup_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.

How do I block lookup_events completely? +

Set action: deny in the PolicyLayer policy for lookup_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.

What MCP server provides lookup_events? +

lookup_events is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon EKS MCP Server tool call.

Start from Amazon EKS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon EKS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.