Find nearest relevant airports to a specific location
AI agents call nearest-airports 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 geographic and airport information without side effects. It queries existing data (airport locations relative to a coordinate) and returns results. No data is created, modified, deleted, or financial transactions initiated. This is a simple lookup/search operation, consistent with Read category tools like 'get' and 'fetch'.
From the tool's definition Tool description states 'Find nearest relevant airports to a specific location' - a straightforward data retrieval operation with no modification, deletion, or execution of external code. Retrieval of airport information from the Amadeus API.
Documented attack patterns abuse exactly the kind of access nearest-airports 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 nearest-airports:
{
"version": "1",
"default": "deny",
"tools": {
"nearest-airports": {}
}
}nearest-airports 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 nearest relevant airports to a specific location. 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 nearest-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 Amadeus MCP Server. Nothing to install.
nearest-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 nearest-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 nearest-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.
nearest-airports 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.