opensky.traffic.aircraft_track
Retrieve the flight trajectory (sequence of GPS waypoints) for a specific aircraft identified by its ICAO24 hex address. Each waypoint contains Unix timestamp, latitude, longitude, barometric altitude (meters), true track angle, and on-ground flag. Use time=0 or omit for the current active flight...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opensky.traffic.aircraft-track.md
What opensky.traffic.aircraft_track does on Apibase
AI agents call opensky.traffic.aircraft_track 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 |
|---|---|---|---|
time | integer | — | Unix timestamp for which to retrieve the track. Use 0 or omit for the current flight trajectory. |
icao24 | string | Yes | ICAO 24-bit hex address of the aircraft (e.g. 3ffc33). Must be an actively tracked flight. |
Parameters from the server's own tool schema.
Why opensky.traffic.aircraft_track is rated Low
Passively retrieves publicly available aircraft tracking data with no side effects or modifications.
From the tool's definition Retrieve flight trajectory, GPS waypoints, Unix timestamp, latitude, longitude. No auth, open access.
Attacks that exploit this kind of access
The rule that runs opensky.traffic.aircraft_track 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_track, this is the rule to start with:
opensky.traffic.aircraft_track 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_track call is checked against it from then on.
Questions about opensky.traffic.aircraft_track
Retrieve the flight trajectory (sequence of GPS waypoints) for a specific aircraft identified by its ICAO24 hex address. Each waypoint contains Unix timestamp, latitude, longitude, barometric altitude (meters), true track angle, and on-ground flag. Use time=0 or omit for the current active flight track. Requires the aircraft to be actively tracked by the OpenSky network. Useful for reconstructing a flight path, computing distance flown, or detecting airport arrivals and departures. 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_track accepts 2 parameters: time, 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_track: 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_track 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_track 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_track. 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_track 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