nominatim_reverse
Reverse geocode coordinates to an address using OpenStreetMap Nominatim.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/nominatim-reverse.md
What nominatim_reverse does on UnClick
AI agents call nominatim_reverse to retrieve information from UnClick 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 |
|---|---|---|---|
latitude | number | Yes | Latitude. |
longitude | number | Yes | Longitude. |
Parameters from the server's own tool schema.
Why nominatim_reverse is rated Low
This is a pure read operation that queries OpenStreetMap Nominatim to retrieve address information from geographic coordinates. There are no side effects—it does not create, modify, delete, or execute code. The action is informational only. Low severity because misuse would only return address information with no ability to harm systems or cause financial damage.
From the tool's definition Tool description states it 'Reverse geocode coordinates to an address' which is a query operation that retrieves location data. Nominatim is a read-only geocoding service that returns address information based on input coordinates with no data modification.
Attacks that exploit this kind of access
The rule that runs nominatim_reverse safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nominatim_reverse, this is the rule to start with:
nominatim_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 UnClick, apply this rule, and every nominatim_reverse call is checked against it from then on.
Questions about nominatim_reverse
Reverse geocode coordinates to an address using OpenStreetMap Nominatim. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
nominatim_reverse 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 UnClick MCP server in PolicyLayer and add a rule for nominatim_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 UnClick. Nothing to install.
nominatim_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_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_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_reverse is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue