Get direct routes from an airport
AI agents call airport_routes to retrieve information from Travel Amadeus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and returns existing airport route information. It has no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions. It is purely informational/reference data retrieval, consistent with other Read category tools like 'airline_lookup' and 'airport_city_search' on the same server.
From the tool's definition Tool name 'airport_routes' and description 'Get direct routes from an airport' indicate a read-only query operation that retrieves flight route data without creating, modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get direct routes from an airport. It is categorised as a Read tool in the Travel Amadeus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Amadeus MCP Server MCP server in PolicyLayer and add a rule for airport_routes: 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 Amadeus MCP Server. Nothing to install.
airport_routes 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 airport_routes 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 airport_routes. 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.
airport_routes is provided by the Travel Amadeus MCP Server MCP server (prathush21/travel-amadeus-mcp). 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 →