geo.navigation.route
Get turn-by-turn driving, walking, cycling, or transit directions between two points with distance and time (Geoapify/OSM)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geo.navigation.route.md
What geo.navigation.route does on Apibase
AI agents call geo.navigation.route 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 |
|---|---|---|---|
lang | string | — | Turn-by-turn instruction language (e.g. "en", "de"). Default: English. |
mode | string | — | Travel mode: drive, walk, bicycle, or transit. Default: drive. |
units | string | — | Distance units: metric (km) or imperial (miles). Default: metric. |
dest_lat | number | Yes | Destination latitude (e.g. 48.8566) |
dest_lon | number | Yes | Destination longitude (e.g. 2.3522) |
origin_lat | number | Yes | Start point latitude (e.g. 40.7128) |
origin_lon | number | Yes | Start point longitude (e.g. -74.0060) |
Parameters from the server's own tool schema.
Why geo.navigation.route is rated Low
Retrieves navigation data without modifying external systems or triggering financial transactions.
From the tool's definition Get turn-by-turn directions between two points with distance and time
Attacks that exploit this kind of access
The rule that runs geo.navigation.route 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 geo.navigation.route, this is the rule to start with:
geo.navigation.route 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 geo.navigation.route call is checked against it from then on.
Questions about geo.navigation.route
Get turn-by-turn driving, walking, cycling, or transit directions between two points with distance and time (Geoapify/OSM). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geo.navigation.route accepts 7 parameters: lang, mode, units, dest_lat, dest_lon, origin_lat, origin_lon. Required: dest_lat, dest_lon, origin_lat, origin_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 geo.navigation.route: 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.
geo.navigation.route 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 geo.navigation.route 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 geo.navigation.route. 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.
geo.navigation.route 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