mapbox_geocode_reverse
Convert coordinates to a place name or address using Mapbox reverse geocoding.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mapbox-geocode-reverse.md
What mapbox_geocode_reverse does on UnClick
AI agents call mapbox_geocode_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 |
|---|---|---|---|
types | string | — | Filter by feature types |
language | string | — | Language for results |
latitude | number | Yes | Latitude |
longitude | number | Yes | Longitude |
access_token | string | Yes | Mapbox access token |
Parameters from the server's own tool schema.
Why mapbox_geocode_reverse is rated Low
This is a reverse geocoding lookup that retrieves read-only data from Mapbox. It takes coordinates as input and returns location information, which is a classic Read operation (search/query). There is no data modification, deletion, code execution, financial impact, or destructive capability. Misuse would be limited to information gathering about locations.
From the tool's definition Tool description states 'Convert coordinates to a place name or address' - a pure query operation that retrieves geographic data based on input coordinates with no side effects or modifications.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs mapbox_geocode_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 mapbox_geocode_reverse, this is the rule to start with:
mapbox_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 UnClick, apply this rule, and every mapbox_geocode_reverse call is checked against it from then on.
Questions about mapbox_geocode_reverse
Convert coordinates to a place name or address using Mapbox reverse geocoding. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mapbox_geocode_reverse accepts 5 parameters: types, language, latitude, longitude, access_token. Required: latitude, longitude, access_token. 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 mapbox_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 UnClick. Nothing to install.
mapbox_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 mapbox_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 mapbox_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.
mapbox_geocode_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