most_connected_airports
Airports ranked by number of nonstop destinations served, worldwide or within one country.
This record as markdown: /tools/com-flywhereto-mcp/most-connected-airports.md
What most_connected_airports does on Fly Where To?
AI agents call most_connected_airports 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 |
|---|---|---|---|
limit | integer | — | How many airports to return (default 10) |
country | string | — | Restrict to one ISO 3166-1 alpha-2 country code, e.g. "SE" |
Parameters from the server's own tool schema.
Why most_connected_airports is rated Low
Even though most_connected_airports 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 most_connected_airports 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 most_connected_airports, this is the rule to start with:
most_connected_airports 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 most_connected_airports call is checked against it from then on.
Questions about most_connected_airports
Airports ranked by number of nonstop destinations served, worldwide or within one country. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
most_connected_airports accepts 2 parameters: limit, country. 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 most_connected_airports: 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.
most_connected_airports 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 most_connected_airports 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 most_connected_airports. 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.
most_connected_airports 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