Get detailed information about an airport including location, timezone, and facilities.
AI agents call get_airport_info 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 retrieves and queries airport metadata (location, timezone, facilities) without side effects or capability to modify data, execute commands, or trigger external state changes. It is a straightforward read-only data lookup operation, making it Read category with low severity.
From the tool's definition Tool name 'get_airport_info' and description 'Get detailed information about an airport including location, timezone, and facilities' indicate pure data retrieval with no modification, deletion, or execution of operations.
Attacks that exploit this kind of access
Get detailed information about an airport including location, timezone, and facilities. 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 get_airport_info: 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.
get_airport_info 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 get_airport_info 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 get_airport_info. 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.
get_airport_info 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 →