airport_distance
skypeek: Calculate the great-circle distance between two airports or points. For airport details use lookup_airport. Returns the great-circle distance between two airports (by code) or coordinates, in km, nautical miles and statute miles, with the initial and final true bearings and the midpoint....
This record as markdown: /tools/dev-tanod-tanod/airport-distance.md
What airport_distance does on Tanod
AI agents call airport_distance to retrieve information from Tanod 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 |
|---|---|---|---|
to | object | Yes | Airport code (ICAO, IATA or ident) or {lat, lon}. |
from | object | Yes | Airport code (ICAO, IATA or ident) or {lat, lon}. |
Parameters from the server's own tool schema.
Why airport_distance is rated Low
Even though airport_distance only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs airport_distance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For airport_distance, this is the rule to start with:
airport_distance 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 Tanod, apply this rule, and every airport_distance call is checked against it from then on.
Questions about airport_distance
skypeek: Calculate the great-circle distance between two airports or points. For airport details use lookup_airport. Returns the great-circle distance between two airports (by code) or coordinates, in km, nautical miles and statute miles, with the initial and final true bearings and the midpoint. Input: from and to: each an airport code or {lat, lon}. Informational only: not for flight planning or navigation. A spherical (haversine) distance, within about 0.5 % of the WGS-84 geodesic. Airports: OurAirports (public domain); the data may contain errors and no endorsement is implied. An unknown code is a 422 unknown_airport (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/airport-lookup-flight-distance-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
airport_distance accepts 2 parameters: to, from. Required: to, from. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for airport_distance: 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 Tanod. Nothing to install.
airport_distance 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 airport_distance 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 airport_distance. 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.
airport_distance is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue