search_events
AI agents call search_events to retrieve information from Trip Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are retrieves/queries of data with no side effects. The empty tool description is uninformative, but the context from the server description and tool name pattern (consistent with other search_* tools like search_flights, search_stays, search_activities) strongly suggests this performs an event search query only. No evidence of modifications, deletions, execution, or financial operations.
From the tool's definition Tool name 'search_events' and server description indicating 'enables Claude to plan trips by performing live searches against Google Flights, hotels, vacation rentals, activities, and events' indicates a read-only search operation with no side effects.
Attacks that exploit this kind of access
search_events. It is categorised as a Read tool in the Trip Search MCP Server, which means it retrieves data without modifying state.
Register the Trip Search 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 Trip Search. 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 Trip Search MCP server (nanwer/trip-search-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 →