calculate_route
Calculate ambulance travel distance, ETA, and route geometry (GeoJSON) between an origin and a hospital destination via OpenRouteService, falling back to a haversine-distance estimate if the routing API is unavailable.
This record as markdown: /tools/nitrostack/calculate-route.md
What calculate_route does on Nitrostack
AI agents call calculate_route to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why calculate_route is rated Low
Tool retrieves routing data and distance calculations without modifying external systems or data.
From the tool's definition Calculate ambulance travel distance, ETA, route geometry via OpenRouteService
Attacks that exploit this kind of access
The rule that runs calculate_route safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calculate_route, this is the rule to start with:
calculate_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 Nitrostack, apply this rule, and every calculate_route call is checked against it from then on.
Questions about calculate_route
Calculate ambulance travel distance, ETA, and route geometry (GeoJSON) between an origin and a hospital destination via OpenRouteService, falling back to a haversine-distance estimate if the routing API is unavailable. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.
Register the Nitrostack MCP server in PolicyLayer and add a rule for calculate_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 Nitrostack. Nothing to install.
calculate_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 calculate_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 calculate_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.
calculate_route is provided by the Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue