# 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.

Agent View of the PolicyLayer registry record for `route_details`. HTML page: https://policylayer.com/tools/com-flywhereto-mcp/route-details

## Facts

- Tool: `route_details`
- Server: Fly Where To? (`https://flywhereto.com/api/mcp`) — https://policylayer.com/tools/com-flywhereto-mcp.md
- Homepage: https://github.com/https://flywhereto.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "route_details",
    "arguments": {
      "origin": "<origin>",
      "destination": "<destination>"
    }
  }
}
```

## 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 signals: Accepts file system path (destination)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Fly Where To?:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "route_details": {}
  }
}
```

## Other tools on Fly Where To? (7)

- `airline_routes` — Read — https://policylayer.com/tools/com-flywhereto-mcp/airline-routes.md
- `destinations_from` — Read — https://policylayer.com/tools/com-flywhereto-mcp/destinations-from.md
- `find_airport` — Read — https://policylayer.com/tools/com-flywhereto-mcp/find-airport.md
- `find_connections` — Read — https://policylayer.com/tools/com-flywhereto-mcp/find-connections.md
- `find_meetup` — Read — https://policylayer.com/tools/com-flywhereto-mcp/find-meetup.md
- `most_connected_airports` — Read — https://policylayer.com/tools/com-flywhereto-mcp/most-connected-airports.md
- `reachable_from` — Read — https://policylayer.com/tools/com-flywhereto-mcp/reachable-from.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-flywhereto-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-flywhereto-mcp