check_eligibility
Check if a flight qualifies for EU261 delay compensation and compute the € amount
This record as markdown: /tools/dev-danielsuchan-eu261/check-eligibility.md
What check_eligibility does on EU261 Flight Compensation
AI agents call check_eligibility to retrieve information from EU261 Flight Compensation 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 |
|---|---|---|---|
origin | string | Yes | Origin airport IATA code (e.g. VIE) |
destination | string | Yes | Destination airport IATA code (e.g. JFK) |
carrier_country | string | — | Carrier's home country code (e.g. AT for Austrian) |
arrival_delay_minutes | number | Yes | Arrival delay in minutes (0 = on time) |
Parameters from the server's own tool schema.
Why check_eligibility is rated Low
This is a read-only operation that retrieves or derives information (eligibility status and compensation amount) from flight data. While the financial context is significant (EU261 compensation claims can involve substantial sums), the tool itself performs no financial transaction, payment processing, or irreversible action. It informs decision-making rather than committing funds.
From the tool's definition Tool description states 'Check if a flight qualifies for EU261 delay compensation and compute the € amount' — it queries eligibility and calculates compensation values without modifying any data or executing external operations.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs check_eligibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EU261 Flight Compensation, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_eligibility, this is the rule to start with:
check_eligibility 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 EU261 Flight Compensation, apply this rule, and every check_eligibility call is checked against it from then on.
Questions about check_eligibility
Check if a flight qualifies for EU261 delay compensation and compute the € amount. It is categorised as a Read tool in the EU261 Flight Compensation MCP Server, which means it retrieves data without modifying state.
check_eligibility accepts 4 parameters: origin, destination, carrier_country, arrival_delay_minutes. Required: origin, destination, arrival_delay_minutes. The full parameter table on this page comes from the server's own tool schema.
Register the EU261 Flight Compensation MCP server in PolicyLayer and add a rule for check_eligibility: 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 EU261 Flight Compensation. Nothing to install.
check_eligibility 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 check_eligibility 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 check_eligibility. 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.
check_eligibility is provided by the EU261 Flight Compensation MCP server (https://eu261.danielsuchan.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EU261 Flight Compensation, and thousands of servers like it.
This server
Across the catalogue