get_flights_by_aircraft
AI agents call get_flights_by_aircraft 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.
The tool name begins with 'get_', which in API conventions indicates a read/retrieval operation. No description is provided, which lowers confidence slightly, but the name strongly suggests querying flight history or data associated with a specific aircraft identifier. This would retrieve data without modifying or executing external operations.
From the tool's definition Tool name 'get_flights_by_aircraft' indicates a retrieval operation. Sibling tools on the server include read operations (get_arrivals_by_airport, get_departures_by_airport, get_callsign, get_closest, get_faa_entry, get_flights_from_interval) and…
Attacks that exploit this kind of access
get_flights_by_aircraft. 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_flights_by_aircraft: 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_flights_by_aircraft 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_flights_by_aircraft 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_flights_by_aircraft. 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_flights_by_aircraft 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 →