mapbox_get_directions
Get turn-by-turn directions between two or more locations using Mapbox.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mapbox-get-directions.md
What mapbox_get_directions does on UnClick
AI agents call mapbox_get_directions 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 |
|---|---|---|---|
steps | boolean | — | Include turn-by-turn steps |
profile | string | — | Routing profile (default: mapbox/driving) |
language | string | — | Language for instructions |
overview | string | — | Route overview geometry detail |
coordinates | string | Yes | Semicolon-separated lng,lat pairs (e.g. -122.4194,37.7749;-118.2437,34.0522) |
access_token | string | Yes | Mapbox access token |
alternatives | boolean | — | Return alternative routes |
Parameters from the server's own tool schema.
Why mapbox_get_directions is rated Low
This tool retrieves navigation/routing information from Mapbox based on location inputs. It is a read-only query that returns computed directions without creating, modifying, deleting data, or executing arbitrary operations. The blast radius is minimal—misuse would at worst generate unwanted API calls, not compromise data or systems.
From the tool's definition Tool name 'mapbox_get_directions' and description 'Get turn-by-turn directions between two or more locations' indicates a query operation that retrieves directional data without modifying, executing code, or causing side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs mapbox_get_directions 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_get_directions, this is the rule to start with:
mapbox_get_directions 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_get_directions call is checked against it from then on.
Questions about mapbox_get_directions
Get turn-by-turn directions between two or more locations using Mapbox. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mapbox_get_directions accepts 7 parameters: steps, profile, language, overview, coordinates, access_token, alternatives. Required: coordinates, 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_get_directions: 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_get_directions 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_get_directions 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_get_directions. 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_get_directions 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