geo.navigation.isochrone
Get reachability area (isochrone) — polygon showing how far you can travel from a point in a given time or distance (Geoapify/OSM)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geo.navigation.isochrone.md
What geo.navigation.isochrone does on Apibase
AI agents call geo.navigation.isochrone 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 | Center point latitude (e.g. 52.5200) |
lon | number | Yes | Center point longitude (e.g. 13.4050) |
mode | string | — | Travel mode: drive, walk, or bicycle. Default: drive. |
time | integer | — | Reachability time in seconds (default 900 = 15 min, max 7200 = 2h). Mutually exclusive with distance. |
distance | integer | — | Reachability distance in meters (max 100km). Mutually exclusive with time. |
Parameters from the server's own tool schema.
Why geo.navigation.isochrone is rated Low
Queries geographic reachability data without modifying state or triggering external operations.
From the tool's definition Get reachability area, polygon showing how far you can travel from a point
Attacks that exploit this kind of access
The rule that runs geo.navigation.isochrone 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.isochrone, this is the rule to start with:
geo.navigation.isochrone 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.isochrone call is checked against it from then on.
Questions about geo.navigation.isochrone
Get reachability area (isochrone) — polygon showing how far you can travel from a point in a given time or distance (Geoapify/OSM). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geo.navigation.isochrone accepts 5 parameters: lat, lon, mode, time, distance. 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 geo.navigation.isochrone: 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.isochrone 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.isochrone 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.isochrone. 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.isochrone 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