Convert an address, place name, street, or intersection into coordinates and structured location results. Use when input is text and you need coordinates before routing, weather, or search. Supports street-level resolution and proximity biasing.
AI agents call 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 data retrieval operation that translates text addresses into geographic coordinates. It reads and returns data without modifying, deleting, or executing external operations. The tool has no side effects and minimal blast radius if misused—it can only return location coordinates, which is public-facing geographic information. This clearly falls under the Read category.
From the tool's definition Tool description states it converts "address, place name, street, or intersection into coordinates and structured location results" with no indication of data modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Convert an address, place name, street, or intersection into coordinates and structured location results. Use when input is text and you need coordinates before routing, weather, or search. Supports street-level resolution and proximity biasing. 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 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.
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 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 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.
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 →