get_arrivals_by_airport
AI agents call get_arrivals_by_airport to retrieve information from Skyfly MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries arrival information by airport—a read operation with no side effects. No data is created, modified, deleted, or executed. The confidence is slightly reduced because the tool description is empty, but the name and server context strongly suggest a straightforward read operation.
From the tool's definition Tool name 'get_arrivals_by_airport' indicates a query operation that retrieves arrival data for a specific airport. The server context describes 'real-time aircraft tracking data' and 'queries that merge live flight positions', consistent with data retrieval.
Attacks that exploit this kind of access
get_arrivals_by_airport. It is categorised as a Read tool in the Skyfly MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Skyfly MCP Server MCP server in PolicyLayer and add a rule for get_arrivals_by_airport: 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 Skyfly MCP Server. Nothing to install.
get_arrivals_by_airport 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 get_arrivals_by_airport 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 get_arrivals_by_airport. 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.
get_arrivals_by_airport is provided by the Skyfly MCP Server MCP server (vog01r/skyfly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →