Search for airport and flight information using Google Flights
AI agents call airports-search to retrieve information from Google Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches for publicly available airport and flight information, which is a read-only operation. It retrieves data without creating, modifying, deleting, or executing any actions. The search functionality has minimal blast radius if misused by an AI agent, as it only returns information without affecting any systems or resources.
From the tool's definition Tool name 'airports-search' and description 'Search for airport and flight information using Google Flights' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Search for airport and flight information using Google Flights. It is categorised as a Read tool in the Google Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Services MCP Server MCP server in PolicyLayer and add a rule for airports-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 Google Services MCP Server. Nothing to install.
airports-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 airports-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 airports-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.
airports-search is provided by the Google Services MCP Server MCP server (ricleedo/google-service-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 →