Get all flights on a specific route. Shows all airlines flying between two airports.
AI agents call get_flights_by_route to retrieve information from Travel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves flight information between airports without creating, modifying, deleting, or executing any operations. It is purely informational, similar to sibling tools like 'search_flights' and 'get_airport_info'. The low severity reflects minimal risk even if misused by an AI agent, as the operation only returns read-only travel data.
From the tool's definition Tool description states 'Get all flights on a specific route. Shows all airlines flying between two airports.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all flights on a specific route. Shows all airlines flying between two airports. It is categorised as a Read tool in the Travel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel MCP Server MCP server in PolicyLayer and add a rule for get_flights_by_route: 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 MCP Server. Nothing to install.
get_flights_by_route 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 get_flights_by_route 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 get_flights_by_route. 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.
get_flights_by_route is provided by the Travel MCP Server MCP server (lev-corrupted/travel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →