# check_eligibility

Check if a flight qualifies for EU261 delay compensation and compute the € amount

Agent View of the PolicyLayer registry record for `check_eligibility`. HTML page: https://policylayer.com/tools/dev-danielsuchan-eu261/check-eligibility

## Facts

- Tool: `check_eligibility`
- Server: EU261 Flight Compensation (`https://eu261.danielsuchan.dev/mcp`) — https://policylayer.com/tools/dev-danielsuchan-eu261.md
- Homepage: https://github.com/MrSucik/eu261-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 4 (3 required)
- Recommended policy verdict: Allowed

## Parameters

| 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 | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "check_eligibility",
    "arguments": {
      "origin": "<origin>",
      "destination": "<destination>",
      "arrival_delay_minutes": 0
    }
  }
}
```

## 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 own 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 signals: Accepts file system path (destination)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches EU261 Flight Compensation:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_eligibility": {}
  }
}
```

## Other tools on EU261 Flight Compensation (5)

- `compute_ev` — Read — https://policylayer.com/tools/dev-danielsuchan-eu261/compute-ev.md
- `distance` — Read — https://policylayer.com/tools/dev-danielsuchan-eu261/distance.md
- `get_price_history` — Read — https://policylayer.com/tools/dev-danielsuchan-eu261/get-price-history.md
- `list_airports` — Read — https://policylayer.com/tools/dev-danielsuchan-eu261/list-airports.md
- `record_price` — Write — https://policylayer.com/tools/dev-danielsuchan-eu261/record-price.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-danielsuchan-eu261 · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-danielsuchan-eu261