record_price
Store a fare observation for trend tracking (builds price history in DO state)
This record as markdown: /tools/dev-danielsuchan-eu261/record-price.md
What record_price does on EU261 Flight Compensation
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
route | string | Yes | Route, e.g. VIE-JFK |
source | string | — | 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.
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 definition Store a fare observation for trend tracking (builds price history in DO state)
Attacks that exploit this kind of access
The rule that runs record_price 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 record_price, this is the rule to start with:
record_price stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 record_price call is checked against it from then on.
Questions about record_price
Store a fare observation for trend tracking (builds price history in DO state). It is categorised as a Write tool in the EU261 Flight Compensation MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
record_price accepts 5 parameters: route, source, carrier, routing, fare_eur. Required: route, carrier, routing, fare_eur. 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 record_price: 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.
record_price is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_price 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 record_price. 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.
record_price 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