Search for flights using the Aviasales Flight Search API.
AI agents call search_flights to retrieve information from Flights MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves flight information in response to search parameters. Searching is a read-only operation that does not modify, delete, execute code, or commit financial transactions. No booking or payment occurs at this stage. Confidence is high because the description explicitly uses the word 'Search' and the name clearly indicates a retrieval operation.
From the tool's definition Tool name 'search_flights' and description 'Search for flights using the Aviasales Flight Search API' indicate a query/search operation with no side effects.
Documented attack patterns abuse exactly the kind of access search_flights gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flights MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_flights:
{
"version": "1",
"default": "deny",
"tools": {
"search_flights": {}
}
}search_flights is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for flights using the Aviasales Flight Search API. It is categorised as a Read tool in the Flights MCP MCP Server, which means it retrieves data without modifying state.
Register the Flights MCP server in PolicyLayer and add a rule for search_flights: 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 Flights MCP. Nothing to install.
search_flights 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 search_flights 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 search_flights. 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.
search_flights is provided by the Flights MCP server (maratsarbasov/flights-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Flights MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Flights MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.