route_details
Which airlines fly nonstop between two airports, with alliance, homepage and the service periods of each. Only periods of kind begins, ends or resumes ever carry dates; scheduled, seasonal and charter periods have none, so seasonal service is unverified for specific travel dates.
This record as markdown: /tools/com-flywhereto-mcp/route-details.md
What route_details does on Fly Where To?
AI agents call route_details 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" |
destination | string | Yes | Three-letter IATA airport code, e.g. "IST" |
Parameters from the server's own tool schema.
Why route_details is rated Low
Even though route_details 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)
Attacks that exploit this kind of access
The rule that runs route_details 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 route_details, this is the rule to start with:
route_details 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 route_details call is checked against it from then on.
Questions about route_details
Which airlines fly nonstop between two airports, with alliance, homepage and the service periods of each. Only periods of kind begins, ends or resumes ever carry dates; scheduled, seasonal and charter periods have none, so seasonal service is unverified for specific travel dates. It is categorised as a Read tool in the Fly Where To? MCP Server, which means it retrieves data without modifying state.
route_details accepts 2 parameters: origin, destination. Required: origin, destination. 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 route_details: 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.
route_details 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 route_details 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 route_details. 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.
route_details 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