# get_price_history

Retrieve stored price history for a route

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

## Facts

- Tool: `get_price_history`
- 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: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `route` | string | yes | Route, e.g. VIE-JFK |

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": "get_price_history",
    "arguments": {
      "route": "<route>"
    }
  }
}
```

## Why get_price_history is rated Low

This tool retrieves historical pricing information for flights on a specific route. It performs a read-only query with no destructive, financial, or executable operations. The worst-case misuse would be information disclosure of price history data, which is a low-severity risk with limited blast radius. Confidence is high due to explicit 'Retrieve' language in the description.

From the tool's own definition: "Tool name 'get_price_history' and description 'Retrieve stored price history for a route' indicate a query operation that retrieves existing data without modification or side effects."

## Use case

AI agents call get_price_history 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": {
    "get_price_history": {}
  }
}
```

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