find_connections
Multi-stop itineraries from an origin airport to either a destination airport or to any airport in a country. Returns airport paths with every airline flying each leg. Airline entries carry their alliance and, when service is not plain scheduled, a kind field (seasonal, charter or suspended). Sus...
This record as markdown: /tools/com-flywhereto-mcp/find-connections.md
What find_connections does on Fly Where To?
AI agents call find_connections 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 |
|---|---|---|---|
origin | string | Yes | Three-letter IATA airport code, e.g. "IST" |
max_stops | integer | — | Maximum intermediate stops (default 2; country searches cap at 2) |
to_country | string | — | ISO 3166-1 alpha-2 country code goal, e.g. "CR" for Costa Rica |
destination | string | — | Three-letter IATA airport code, e.g. "IST" |
same_airline | boolean | — | Require one single airline to operate every leg |
exclude_kinds | array | — | Drop legs whose service kind is in this list, e.g. ["suspended"] or ["suspended","charter"] for currently bookable routes only |
Parameters from the server's own tool schema.
Why find_connections is rated Low
Even though find_connections 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 signalsAccepts file system path (destination) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs find_connections 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_connections, this is the rule to start with:
find_connections 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_connections call is checked against it from then on.
Questions about find_connections
Multi-stop itineraries from an origin airport to either a destination airport or to any airport in a country. Returns airport paths with every airline flying each leg. Airline entries carry their alliance and, when service is not plain scheduled, a kind field (seasonal, charter or suspended). Suspended legs are included and flagged, not excluded; pass exclude_kinds to drop them. Seasonal and charter service carries no operating dates and there is no frequency or days-of-week data, so treat every match as unverified for specific travel dates. Provide exactly one of destination or to_country. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
find_connections accepts 6 parameters: origin, max_stops, to_country, destination, same_airline, exclude_kinds. Required: origin. 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_connections: 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_connections 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_connections 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_connections. 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_connections 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