Geocode multiple locations in a single request.
AI agents call batch_geocode 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.
Geocoding is a data lookup operation that converts location names/addresses to geographic coordinates. It retrieves information without creating, modifying, deleting, executing code, or initiating financial transactions. The batch aspect simply means multiple read operations are grouped efficiently, not a change in the fundamental read-only nature of the operation.
From the tool's definition Tool name 'batch_geocode' and description 'Geocode multiple locations in a single request' indicate a read-only operation that retrieves geographic coordinates for multiple locations without modifying, executing operations, or causing side effects.
Attacks that exploit this kind of access
Geocode multiple locations in a single request. 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 batch_geocode: 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.
batch_geocode 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 batch_geocode 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 batch_geocode. 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.
batch_geocode 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 →