address.geocodio.reverse
Reverse geocode latitude/longitude to a US or Canada address — returns formatted address, parsed components (street, city, state, ZIP, county), accuracy type, and source. Supports multiple results ranked by proximity (Geocodio)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/address.geocodio.reverse.md
What address.geocodio.reverse does on Apibase
AI agents call address.geocodio.reverse to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
lat | number | Yes | Latitude (24-72 range for US/Canada, e.g. 38.8976) |
lon | number | Yes | Longitude (negative for Western Hemisphere, e.g. -77.0365) |
limit | integer | — | Max results to return (default 5, max 20) |
Parameters from the server's own tool schema.
Why address.geocodio.reverse is rated Low
Retrieves geographic data from coordinates; no data modification, deletion, or execution side effects.
From the tool's definition Reverse geocode latitude/longitude to a US or Canada address — returns formatted address
Attacks that exploit this kind of access
The rule that runs address.geocodio.reverse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For address.geocodio.reverse, this is the rule to start with:
address.geocodio.reverse is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every address.geocodio.reverse call is checked against it from then on.
Questions about address.geocodio.reverse
Reverse geocode latitude/longitude to a US or Canada address — returns formatted address, parsed components (street, city, state, ZIP, county), accuracy type, and source. Supports multiple results ranked by proximity (Geocodio). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
address.geocodio.reverse accepts 3 parameters: lat, lon, limit. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for address.geocodio.reverse: 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 Apibase. Nothing to install.
address.geocodio.reverse 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 address.geocodio.reverse 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 address.geocodio.reverse. 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.
address.geocodio.reverse is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue