opensky.traffic.aircraft_state
Get the current real-time ADS-B state vector for a single aircraft identified by its ICAO 24-bit hex address (e.g. 3c6444). Returns position, altitude, speed, heading, vertical rate, squawk, origin country, and whether on ground. If the aircraft is not currently tracked (landed, out of range, or ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opensky.traffic.aircraft-state.md
What opensky.traffic.aircraft_state does on Apibase
AI agents call opensky.traffic.aircraft_state 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 |
|---|---|---|---|
icao24 | string | Yes | ICAO 24-bit hex address of the aircraft transponder (e.g. 3c6444 for a Lufthansa aircraft) |
Parameters from the server's own tool schema.
Why opensky.traffic.aircraft_state is rated Low
Retrieves publicly available aircraft tracking data without side effects or access control.
From the tool's definition Get the current real-time ADS-B state vector for a single aircraft
Attacks that exploit this kind of access
The rule that runs opensky.traffic.aircraft_state 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 opensky.traffic.aircraft_state, this is the rule to start with:
opensky.traffic.aircraft_state 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 opensky.traffic.aircraft_state call is checked against it from then on.
Questions about opensky.traffic.aircraft_state
Get the current real-time ADS-B state vector for a single aircraft identified by its ICAO 24-bit hex address (e.g. 3c6444). Returns position, altitude, speed, heading, vertical rate, squawk, origin country, and whether on ground. If the aircraft is not currently tracked (landed, out of range, or transponder off) the response includes found=false. ICAO24 addresses can be looked up from aircraft registrations (e.g. N-number, D- prefix). Useful for tracking a specific flight in real time. Source: OpenSky Network — opensky-network.org. No auth, open access. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opensky.traffic.aircraft_state accepts 1 parameter: icao24. Required: icao24. 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 opensky.traffic.aircraft_state: 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.
opensky.traffic.aircraft_state 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 opensky.traffic.aircraft_state 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 opensky.traffic.aircraft_state. 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.
opensky.traffic.aircraft_state 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