nominatim.geocode.reverse
Reverse geocode a latitude/longitude pair into the nearest address or place using OpenStreetMap data via Nominatim. Optional zoom controls the level of detail, from country down to individual building. No auth required; ODbL licensed, © OpenStreetMap contributors.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nominatim.geocode.reverse.md
What nominatim.geocode.reverse does on Apibase
AI agents call nominatim.geocode.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 of the point to resolve to an address |
lon | number | Yes | Longitude of the point to resolve to an address |
zoom | integer | — | Level of detail for the resolved address (0=country, 10=city, 18=building, default varies by feature) |
language | string | — | Preferred response language as an Accept-Language value (e.g. "en", "de-DE") |
Parameters from the server's own tool schema.
Why nominatim.geocode.reverse is rated Low
Queries public OpenStreetMap data to retrieve address information without side effects.
From the tool's definition Reverse geocode latitude/longitude pair into nearest address; no auth required.
Attacks that exploit this kind of access
The rule that runs nominatim.geocode.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 nominatim.geocode.reverse, this is the rule to start with:
nominatim.geocode.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 nominatim.geocode.reverse call is checked against it from then on.
Questions about nominatim.geocode.reverse
Reverse geocode a latitude/longitude pair into the nearest address or place using OpenStreetMap data via Nominatim. Optional zoom controls the level of detail, from country down to individual building. No auth required; ODbL licensed, © OpenStreetMap contributors. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nominatim.geocode.reverse accepts 4 parameters: lat, lon, zoom, language. 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 nominatim.geocode.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.
nominatim.geocode.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 nominatim.geocode.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 nominatim.geocode.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.
nominatim.geocode.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