opensky_flights
Get flight history from OpenSky Network for a time range (max 2 hours).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/opensky-flights.md
What opensky_flights does on UnClick
AI agents call opensky_flights 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 |
|---|---|---|---|
end | number | Yes | End time (Unix timestamp). |
begin | number | Yes | Start time (Unix timestamp). |
icao24 | string | — | Filter by ICAO24 transponder address. |
Parameters from the server's own tool schema.
Why opensky_flights is rated Low
This tool retrieves flight history data from a public aviation data source with no side effects, no ability to modify records, execute commands, delete data, or commit financial transactions. The read-only nature and public data source make this a low-severity Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states "Get flight history from OpenSky Network for a time range (max 2 hours)" - the verb "Get" indicates data retrieval with no modification or deletion. The functionality is querying historical flight data within a bounded time window.
Attacks that exploit this kind of access
The rule that runs opensky_flights 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_flights, this is the rule to start with:
opensky_flights 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_flights call is checked against it from then on.
Questions about opensky_flights
Get flight history from OpenSky Network for a time range (max 2 hours). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
opensky_flights accepts 3 parameters: end, begin, icao24. Required: end, begin. 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_flights: 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_flights 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_flights 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_flights. 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_flights 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