Search specifically for airports and cities
AI agents call airport_city_search 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 retrieves reference data about airports and cities. Search operations that query reference data without side effects are categorized as Read. The low severity reflects minimal risk: misuse would return unwanted but non-harmful airport/city information. No financial, destructive, or system-level impacts are possible.
From the tool's definition Tool is named 'airport_city_search' and described as 'Search specifically for airports and cities' — performs a search query with no indication of data modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Search specifically for airports and cities. 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_city_search: 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_city_search 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_city_search 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_city_search. 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_city_search 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 →