search_activities
AI agents call search_activities 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.
Despite the empty description, the tool name and server context strongly indicate this performs a search/query operation to retrieve activity information for trip planning. This is consistent with sibling search tools (search_flights, search_stays, search_events) which are Read operations. No evidence suggests data modification, deletion, execution of arbitrary code, or financial transactions.
From the tool's definition Tool name 'search_activities' combined with server context of travel planning tools (search_flights, search_stays, search_events); pattern matches other Read operations like search_events and search_stays which query external data without modification.
Attacks that exploit this kind of access
search_activities. 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_activities: 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_activities 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_activities 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_activities. 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_activities 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 →