Retrieves the operational status of arriving flights at Incheon Airport. You can search by flight ID or origin airport code. If no date is specified, it defaults to today's date. (e.g., 20250910)
Part of the Incheon Airport Live server.
Free to start. No card required.
AI agents call get_flight_arrivals to retrieve information from Incheon Airport Live without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_flight_arrivals only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_flight_arrivals": {}
}
}See the full Incheon Airport Live policy for all 5 tools.
These attack patterns abuse exactly the kind of access get_flight_arrivals gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Retrieves the operational status of arriving flights at Incheon Airport. You can search by flight ID or origin airport code. If no date is specified, it defaults to today's date. (e.g., 20250910). It is categorised as a Read tool in the Incheon Airport Live MCP Server, which means it retrieves data without modifying state.
Register the Incheon Airport Live MCP server in PolicyLayer and add a rule for get_flight_arrivals: 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 Incheon Airport Live. Nothing to install.
get_flight_arrivals 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_flight_arrivals 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_flight_arrivals. 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_flight_arrivals is provided by the Incheon Airport Live MCP server (AITutor3/icn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Incheon Airport Live tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.