Search for airports and cities with autocomplete (useful for finding IATA codes)
AI agents call location_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 travel reference data (airport and city information) to assist users in finding IATA codes. It performs a search/lookup query with no capacity to modify, execute external operations, or cause destructive actions. The low severity reflects minimal risk from misuse—returning incorrect location suggestions would not cause financial harm or irreversible damage.
From the tool's definition Tool description states 'Search for airports and cities with autocomplete' and 'useful for finding IATA codes'.
Attacks that exploit this kind of access
Search for airports and cities with autocomplete (useful for finding IATA codes). 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 location_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.
location_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 location_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 location_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.
location_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 →