# record_price

Store a fare observation for trend tracking (builds price history in DO state)

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

## Facts

- Tool: `record_price`
- 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: Write (Medium risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 5 (4 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `route` | string | yes | Route, e.g. VIE-JFK |
| `source` | string | no | e.g. 'Google Flights' |
| `carrier` | string | yes |  |
| `routing` | string | yes | e.g. 'nonstop' or '1-stop via FRA' |
| `fare_eur` | number | yes |  |

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": "record_price",
    "arguments": {
      "route": "<route>",
      "carrier": "<carrier>",
      "routing": "<routing>",
      "fare_eur": 0
    }
  }
}
```

## Why record_price is rated Medium

The tool writes/stores data (a fare observation) into persistent state for trend tracking purposes. This is a reversible write operation with no financial transaction, code execution, or destructive action. Severity is low because it only records price data for analytics, with limited blast radius if misused.

From the tool's own definition: "Store a fare observation for trend tracking (builds price history in DO state)"

## Use case

AI agents use record_price to create or update resources in EU261 Flight Compensation, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EU261 Flight Compensation environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_price": {
      "limits": [
        {
          "counter": "record_price_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on EU261 Flight Compensation (5)

- `check_eligibility` — Read — https://policylayer.com/tools/dev-danielsuchan-eu261/check-eligibility.md
- `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

## 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