find_airport
Look up airports by IATA/ICAO code or by name fragment. Returns code, name, country, coordinates and how many nonstop destinations each serves. Use this first when you only have a city or airport name.
This record as markdown: /tools/com-flywhereto-mcp/find-airport.md
What find_airport does on Fly Where To?
AI agents call find_airport to retrieve information from Fly Where To? 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 |
|---|---|---|---|
query | string | Yes | IATA code ("IST"), ICAO code ("LTFM") or part of an airport name ("istanbul") |
Parameters from the server's own tool schema.
Why find_airport is rated Low
Even though find_airport 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 find_airport safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fly Where To?, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_airport, this is the rule to start with:
find_airport 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 Fly Where To?, apply this rule, and every find_airport call is checked against it from then on.
Questions about find_airport
Look up airports by IATA/ICAO code or by name fragment. Returns code, name, country, coordinates and how many nonstop destinations each serves. Use this first when you only have a city or airport name. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
find_airport accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Fly Where To? MCP server in PolicyLayer and add a rule for find_airport: 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 Fly Where To?. Nothing to install.
find_airport 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 find_airport 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 find_airport. 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.
find_airport is provided by the Fly Where To? MCP server (https://flywhereto.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fly Where To?, and thousands of servers like it.
This server
Across the catalogue