search_airports
Search for airports by city name or airport code. Useful for finding IATA codes.
This record as markdown: /tools/nitrostack/search-airports.md
What search_airports does on Nitrostack
AI agents call search_airports to retrieve information from Nitrostack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_airports is rated Low
This tool retrieves airport information (IATA codes, locations) in response to search parameters. It performs a read-only lookup without creating, modifying, deleting, or executing any operations. The low severity reflects minimal blast radius if misused—an AI agent could retrieve irrelevant or excessive airport data, but this poses no security, financial, or destructive risk.
From the tool's definition Tool name 'search_airports' combined with description 'Search for airports by city name or airport code' indicates a query/lookup operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_airports safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nitrostack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_airports, this is the rule to start with:
search_airports is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nitrostack, apply this rule, and every search_airports call is checked against it from then on.
Questions about search_airports
Search for airports by city name or airport code. Useful for finding IATA codes. It is categorised as a Read tool in the Nitrostack MCP Server, which means it retrieves data without modifying state.
Register the Nitrostack 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 Nitrostack. 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 Nitrostack MCP server (nitrocloudofficial/nitrostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nitrostack, and thousands of servers like it.
This server
Across the catalogue