get_departures_by_airport
AI agents call get_departures_by_airport to retrieve information from Adsb Lol 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 departure information for a given airport. Based on the 'get_' prefix and sibling tools that are clearly read-only queries (get_arrivals_by_airport, get_flights_by_aircraft, get_callsign), this is a data retrieval operation with no side effects.
From the tool's definition Tool name 'get_departures_by_airport' indicates a query/retrieval operation. No description provided, but the naming pattern ('get_*') and the context of sibling tools (all variants of get_* for flight data queries) strongly suggest this retrieves departure…
Attacks that exploit this kind of access
get_departures_by_airport. It is categorised as a Read tool in the Adsb Lol MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Adsb Lol MCP Server MCP server in PolicyLayer and add a rule for get_departures_by_airport: 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 Adsb Lol MCP Server. Nothing to install.
get_departures_by_airport 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_departures_by_airport 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_departures_by_airport. 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_departures_by_airport is provided by the Adsb Lol MCP Server MCP server (x86ed/adsb.lol-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 →