Geocode multiple addresses, intersections, or place queries in one request with structured per-record results. Use for bulk operations instead of repeated single geocode calls. Max 50 per batch.
AI agents call batch_geocode to retrieve information from ThinAir Geo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Geocoding is a lookup operation that converts addresses into geographic coordinates. batch_geocode retrieves location data in bulk without side effects, state changes, or irreversible actions. Maximum batch size of 50 is a rate-limiting constraint, not a severity factor. This is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'geocode[s] multiple addresses' and 'structured per-record results' with no mention of modifying, deleting, or executing operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Geocode multiple addresses, intersections, or place queries in one request with structured per-record results. Use for bulk operations instead of repeated single geocode calls. Max 50 per batch. It is categorised as a Read tool in the ThinAir Geo MCP Server, which means it retrieves data without modifying state.
Register the ThinAir Geo 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 ThinAir Geo. 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 ThinAir Geo MCP server (thinairtelematics/thinair-geo). 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 →