search_events
AI agents call search_events to retrieve information from Luma Events without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool searches for events by various filters (category, city, distance, keywords) which is a read-only query operation with no side effects. It discovers and returns event information. The empty description slightly reduces confidence, but the context from the server description and sibling tools (get_event for retrieval, export_event_ics for export) strongly suggests a read operation.
From the tool's definition Tool name 'search_events' combined with server description stating 'search by category, city, distance, and keywords' and sibling tools that include 'get_event' and 'export_event_ics' indicate this retrieves event data without modification.
Attacks that exploit this kind of access
search_events. It is categorised as a Read tool in the Luma Events MCP Server, which means it retrieves data without modifying state.
Register the Luma Events MCP server in PolicyLayer and add a rule for search_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 Luma Events. Nothing to install.
search_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 search_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 search_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.
search_events is provided by the Luma Events MCP server (alx1p/luma-cal-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 →