airline_routes
The full network one airline flies: every origin with its nonstop destinations, as IATA codes. Look up by IATA airline code ("TK") or name fragment ("turkish"). Ambiguous queries return a candidate list to refine from.
This record as markdown: /tools/com-flywhereto-mcp/airline-routes.md
What airline_routes does on Fly Where To?
AI agents call airline_routes 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 |
|---|---|---|---|
airline | string | Yes | Airline IATA code ("TK", "W6") or part of the airline name ("turkish") |
Parameters from the server's own tool schema.
Why airline_routes is rated Low
Even though airline_routes 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs airline_routes 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 airline_routes, this is the rule to start with:
airline_routes 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 airline_routes call is checked against it from then on.
Questions about airline_routes
The full network one airline flies: every origin with its nonstop destinations, as IATA codes. Look up by IATA airline code ("TK") or name fragment ("turkish"). Ambiguous queries return a candidate list to refine from. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
airline_routes accepts 1 parameter: airline. Required: airline. 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 airline_routes: 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.
airline_routes 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 airline_routes 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 airline_routes. 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.
airline_routes 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