This record as markdown: /tools/io-github-whiteknightonhorse-apibase/aviasales.flights.nearby.md
What aviasales.flights.nearby does on Apibase
AI agents call aviasales.flights.nearby 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 | Departure city IATA code (e.g. MOW) |
currency | string | — | Currency code for prices (default usd) |
depart_date | string | — | Departure date in YYYY-MM-DD format |
destination | string | Yes | Target destination IATA code — also searches nearby airports |
flexibility | integer | — | Date flexibility in days (+/- from given dates) |
return_date | string | — | Return date in YYYY-MM-DD format |
Parameters from the server's own tool schema.
Why aviasales.flights.nearby is rated Low
Retrieves flight destination data without modifying, deleting, or executing external actions.
From the tool's definition Find nearby flight destinations; search operation with no side effects.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs aviasales.flights.nearby 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 aviasales.flights.nearby, this is the rule to start with:
aviasales.flights.nearby 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 aviasales.flights.nearby call is checked against it from then on.
Questions about aviasales.flights.nearby
Find nearby flight destinations. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
aviasales.flights.nearby accepts 6 parameters: origin, currency, depart_date, destination, flexibility, return_date. Required: origin, destination. 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 aviasales.flights.nearby: 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.
aviasales.flights.nearby 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 aviasales.flights.nearby 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 aviasales.flights.nearby. 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.
aviasales.flights.nearby 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