Returns all LADD aircraft. https://www.faa.gov/pilots/ladd
AI agents call get_ladd 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 aircraft data from a public FAA registry without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query operation. Severity is low because unauthorized access to publicly-available aircraft registration data poses minimal risk, and there are no side effects from calling this tool.
From the tool's definition Tool name 'get_ladd' and description 'Returns all LADD aircraft' indicate a retrieval operation with no modification of data. The URL reference confirms it queries FAA LADD (Light Aircraft Development and Design) registry information.
Attacks that exploit this kind of access
Returns all LADD aircraft. https://www.faa.gov/pilots/ladd. 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_ladd: 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_ladd 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_ladd 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_ladd. 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_ladd 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 →