Search for airports by city name or location. Returns airport codes, names, and locations.
AI agents call search_airports 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.
This tool only retrieves and queries airport information (codes, names, locations) based on search criteria. It has no side effects, does not modify data, does not execute commands, and does not involve financial transactions. It is a straightforward read operation consistent with search and lookup functions.
From the tool's definition Tool description states it 'Search for airports by city name or location. Returns airport codes, names, and locations.' — purely retrieval operations with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Search for airports by city name or location. Returns airport codes, names, and locations. 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 search_airports: 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.
search_airports 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 search_airports 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 search_airports. 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.
search_airports 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 →