adsbdb.callsign.lookup
Resolve a flight callsign (e.g. "BAW123", "UAL456") to its origin and destination airports plus operating airline. Returns full airport details: ICAO and IATA codes, name, municipality, country, coordinates, and elevation. Also returns airline name, codes, and ATC callsign. Callsigns combine the ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/adsbdb.callsign.lookup.md
What adsbdb.callsign.lookup does on Apibase
AI agents call adsbdb.callsign.lookup to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
callsign | string | Yes | Flight callsign to resolve, typically the airline ICAO code followed by flight number (e.g. "BAW123" for British Airways flight 123, "UAL456" for United flight |
Parameters from the server's own tool schema.
Why adsbdb.callsign.lookup is rated Low
Retrieves publicly available flight routing and airport data with no side effects or modification capabilities.
From the tool's definition Resolve a flight callsign to origin, destination airports, airline details. Returns airport codes, coordinates, airline information.
Attacks that exploit this kind of access
The rule that runs adsbdb.callsign.lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adsbdb.callsign.lookup, this is the rule to start with:
adsbdb.callsign.lookup 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 Apibase, apply this rule, and every adsbdb.callsign.lookup call is checked against it from then on.
Questions about adsbdb.callsign.lookup
Resolve a flight callsign (e.g. "BAW123", "UAL456") to its origin and destination airports plus operating airline. Returns full airport details: ICAO and IATA codes, name, municipality, country, coordinates, and elevation. Also returns airline name, codes, and ATC callsign. Callsigns combine the airline ICAO code with a flight number and are broadcast by ATC transponders. Useful for enriching ADS-B flight tracking data with route context. Source: ADS-B DB — api.adsbdb.com, MIT license, no auth. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
adsbdb.callsign.lookup accepts 1 parameter: callsign. Required: callsign. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for adsbdb.callsign.lookup: 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 Apibase. Nothing to install.
adsbdb.callsign.lookup 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 adsbdb.callsign.lookup 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 adsbdb.callsign.lookup. 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.
adsbdb.callsign.lookup is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue