get_price_history
Retrieve stored price history for a route
This record as markdown: /tools/dev-danielsuchan-eu261/get-price-history.md
What get_price_history does on EU261 Flight Compensation
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
route | string | Yes | Route, e.g. VIE-JFK |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_price_history 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 get_price_history, this is the rule to start with:
get_price_history 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 get_price_history call is checked against it from then on.
Questions about get_price_history
Retrieve stored price history for a route. It is categorised as a Read tool in the EU261 Flight Compensation MCP Server, which means it retrieves data without modifying state.
get_price_history accepts 1 parameter: route. Required: route. 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 get_price_history: 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.
get_price_history 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_price_history 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_price_history. 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_price_history 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