sabre.flights.destinations
Find cheapest flight destinations from an origin airport
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/sabre.flights.destinations.md
What sabre.flights.destinations does on Apibase
AI agents call sabre.flights.destinations to retrieve information from Apibase 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 | Origin airport IATA code (e.g. JFK, LAX) |
max_fare | number | — | Maximum fare in USD to filter results |
return_date | string | Yes | Return date in YYYY-MM-DD format |
point_of_sale | string | — | 2-letter country code for pricing (e.g. US, GB) |
departure_date | string | Yes | Departure date in YYYY-MM-DD format |
Parameters from the server's own tool schema.
Why sabre.flights.destinations is rated Low
Tool queries flight price data with no state changes or irreversible effects.
From the tool's definition Find cheapest flight destinations from an origin airport
Attacks that exploit this kind of access
The rule that runs sabre.flights.destinations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sabre.flights.destinations, this is the rule to start with:
sabre.flights.destinations 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 Apibase, apply this rule, and every sabre.flights.destinations call is checked against it from then on.
Questions about sabre.flights.destinations
Find cheapest flight destinations from an origin airport. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
sabre.flights.destinations accepts 5 parameters: origin, max_fare, return_date, point_of_sale, departure_date. Required: origin, return_date, departure_date. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for sabre.flights.destinations: 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 Apibase. Nothing to install.
sabre.flights.destinations 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 sabre.flights.destinations 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 sabre.flights.destinations. 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.
sabre.flights.destinations is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue