AI agents call search-flights to retrieve information from Travel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves flight information from an external API without creating, modifying, deleting, or executing code. It is a straightforward Read operation with minimal risk—worst case, an AI agent performs unwanted flight searches, generating queries but not committing financial obligations or making actual bookings.
From the tool's definition Tool name is 'search-flights' and description states 'search for flights'. The verb 'search' indicates data retrieval 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 Travel, 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. It is categorised as a Read tool in the Travel MCP Server, which means it retrieves data without modifying state.
Register the Travel 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 Travel. 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 Travel MCP server (prakashsanker/flights-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Travel, 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.
3 Travel tools catalogued and risk-classified — across an index of 43,000+ MCP servers.