Search through previously geocoded locations.
AI agents call search_locations to retrieve information from MCP Travel Planner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'search' combined with 'through previously geocoded locations' indicates a read-only retrieval operation. It queries existing data without creating, modifying, or deleting information. No execution of external commands, financial transactions, or destructive actions are implied. This is a straightforward information lookup tool.
From the tool's definition Tool performs a search operation on previously geocoded locations, which is a query/retrieval action with no data modification or side effects.
Attacks that exploit this kind of access
Search through previously geocoded locations. It is categorised as a Read tool in the MCP Travel Planner MCP Server, which means it retrieves data without modifying state.
Register the MCP Travel Planner MCP server in PolicyLayer and add a rule for search_locations: 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 MCP Travel Planner. Nothing to install.
search_locations 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_locations 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_locations. 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_locations is provided by the MCP Travel Planner MCP server (leonavevor/mcp_travelassistant). 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 →