Convert a latitude/longitude coordinate pair into a street address. Returns the best-match formatted address, address components, and coordinates.
AI agents call reverse_geocode to retrieve information from loc8n Geographic Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
latitude | number | Yes | Latitude in decimal degrees (-90 to 90). |
longitude | number | Yes | Longitude in decimal degrees (-180 to 180). |
Parameters from the server's own tool schema.
This tool performs a lookup/query operation that retrieves geographic data (address information) based on input coordinates. It has no ability to modify, delete, or execute operations. The output is informational only. This is a classic Read operation—similar to geocode_address (its inverse) and other lookup tools in the sibling list.
From the tool's definition Tool description states it 'Convert[s] a latitude/longitude coordinate pair into a street address' and 'Returns the best-match formatted address, address components, and coordinates.' The verb 'Returns' and the read-only nature of converting coordinates to…
Attacks that exploit this kind of access
Convert a latitude/longitude coordinate pair into a street address. Returns the best-match formatted address, address components, and coordinates. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
reverse_geocode accepts 2 parameters: latitude, longitude. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the loc8n Geographic Data MCP server in PolicyLayer and add a rule for reverse_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 loc8n Geographic Data. Nothing to install.
reverse_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 reverse_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 reverse_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.
reverse_geocode is provided by the loc8n Geographic Data MCP server (gener8v/gener8v.mcp.geographic-data). 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 →