opensky_states
Get live aircraft states (position, altitude, velocity) from OpenSky Network.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/opensky-states.md
What opensky_states does on UnClick
AI agents call opensky_states to retrieve information from UnClick 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 |
|---|---|---|---|
lamax | number | — | Bounding box max latitude. |
lamin | number | — | Bounding box min latitude. |
lomax | number | — | Bounding box max longitude. |
lomin | number | — | Bounding box min longitude. |
icao24 | string | — | Filter by ICAO24 transponder address. |
Parameters from the server's own tool schema.
Why opensky_states is rated Low
This tool retrieves publicly available aircraft state information from the OpenSky Network API. It has no side effects, cannot modify data, execute code, delete records, or move money. The blast radius of misuse is minimal—an agent could retrieve aircraft position data at scale, but this is public information. Classified as Read with low severity.
From the tool's definition Tool description states 'Get live aircraft states (position, altitude, velocity)' — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs opensky_states safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opensky_states, this is the rule to start with:
opensky_states 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 UnClick, apply this rule, and every opensky_states call is checked against it from then on.
Questions about opensky_states
Get live aircraft states (position, altitude, velocity) from OpenSky Network. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
opensky_states accepts 5 parameters: lamax, lamin, lomax, lomin, icao24. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for opensky_states: 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 UnClick. Nothing to install.
opensky_states 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_states 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_states. 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_states is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue