get_checkout_quote
Re-price a specific room live against the supplier before checkout (no booking, no charge). Use the supplierRoomId and price/currency from search_hotels. Returns the authoritative grand total, a rateValidUntil timestamp, and any taxes/fees.
This record as markdown: /tools/com-getmyhotels-getmyhotels/get-checkout-quote.md
What get_checkout_quote does on GetMyHotels
AI agents call get_checkout_quote to retrieve information from GetMyHotels 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 |
|---|---|---|---|
ref | string | — | Hotel `ref` from `search_hotels` (e.g. 'TBO:1402689'). Alternative to supplierCode + supplierHotelId. |
rooms | integer | — | Rooms (default 1). |
adults | integer | — | Adults (default 2). |
checkIn | string | Yes | Check-in date, ISO 8601 (YYYY-MM-DD). |
checkOut | string | Yes | Check-out date, ISO 8601 (YYYY-MM-DD). |
children | integer | — | Children (default 0). |
currency | string | Yes | ISO 4217 currency of `price`/`totalPrice` (e.g. 'USD'). |
promoCode | string | — | Optional promo code. |
totalPrice | number | Yes | The room's price from `search_hotels` — the TOTAL for the whole stay, not a nightly rate (used to detect price changes). |
childrenAges | array | — | Age of each child. |
supplierCode | string | — | Supplier code (from `search_hotels`). Required if `ref` is omitted. |
supplierRoomId | string | Yes | Bookable room/rate id from the chosen room in `search_hotels`. |
Parameters from the server's own tool schema.
Why get_checkout_quote is rated Low
This tool queries live pricing data from a supplier and returns pricing details. It performs no creation, modification, deletion, or financial transaction. The emphasis on 'no booking, no charge' explicitly indicates no state changes occur. This is a straightforward Read operation—data retrieval with no side effects. Severity is low because misuse would only retrieve pricing information, posing minimal risk.
From the tool's definition Tool description states it 're-price[s]...before checkout (no booking, no charge)' and 'Returns the authoritative grand total...and any taxes/fees.' The explicit clarifications that there is 'no booking, no charge' confirm this is a read-only retrieval of…
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs get_checkout_quote safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GetMyHotels, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_checkout_quote, this is the rule to start with:
get_checkout_quote 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 GetMyHotels, apply this rule, and every get_checkout_quote call is checked against it from then on.
Questions about get_checkout_quote
Re-price a specific room live against the supplier before checkout (no booking, no charge). Use the supplierRoomId and price/currency from search_hotels. Returns the authoritative grand total, a rateValidUntil timestamp, and any taxes/fees. It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
get_checkout_quote accepts 12 parameters: ref, rooms, adults, checkIn, checkOut, children, currency, promoCode, totalPrice, childrenAges, supplierCode, supplierRoomId. Required: checkIn, checkOut, currency, totalPrice, supplierRoomId. The full parameter table on this page comes from the server's own tool schema.
Register the GetMyHotels MCP server in PolicyLayer and add a rule for get_checkout_quote: 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 GetMyHotels. Nothing to install.
get_checkout_quote 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_checkout_quote 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_checkout_quote. 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_checkout_quote is provided by the GetMyHotels MCP server (https://mcp.getmyhotels.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GetMyHotels, and thousands of servers like it.
This server
Across the catalogue