reachable_from
How far the network stretches from one airport within a stop budget: totals, breakdown by stop count and by country. Pass country to list the individual reachable airports there with their minimum stops.
This record as markdown: /tools/com-flywhereto-mcp/reachable-from.md
What reachable_from does on Fly Where To?
AI agents call reachable_from 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" |
country | string | — | List the reachable airports in this ISO 3166-1 alpha-2 country |
max_stops | integer | — | Maximum intermediate stops (default 1; 0 = nonstop only) |
Parameters from the server's own tool schema.
Why reachable_from is rated Low
Even though reachable_from 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 reachable_from 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 reachable_from, this is the rule to start with:
reachable_from 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 reachable_from call is checked against it from then on.
Questions about reachable_from
How far the network stretches from one airport within a stop budget: totals, breakdown by stop count and by country. Pass country to list the individual reachable airports there with their minimum stops. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
reachable_from accepts 3 parameters: origin, country, max_stops. 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 reachable_from: 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.
reachable_from 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 reachable_from 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 reachable_from. 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.
reachable_from 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