AI agents call airport-routes to retrieve information from 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 retrieves and queries available flight routes from an airport without creating, modifying, deleting, or executing operations. It is a pure data lookup with no capability to book flights, modify reservations, or trigger external actions. The blast radius of misuse is minimal—an AI could only retrieve information about available routes.
From the tool's definition Tool name is 'airport-routes' with description 'Find direct routes from a specific airport' — uses 'find' verb indicating data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access airport-routes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amadeus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for airport-routes:
{
"version": "1",
"default": "deny",
"tools": {
"airport-routes": {}
}
}airport-routes 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.
Find direct routes from a specific airport. It is categorised as a Read tool in the Amadeus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 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 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 Amadeus MCP Server MCP server (privilegemendes/amadeus-mcp-server-standalone). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amadeus MCP Server, 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.
8 Amadeus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.