create_one_click_checkout

SERVERGetMyHotels SOURCEhttps://mcp.getmyhotels.com

Critical RISK CLASS

Category Financial

Parameters 127 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getmyhotels-getmyhotels/create-one-click-checkout.md

WHAT IT DOES

What create_one_click_checkout does on GetMyHotels

AI agents use create_one_click_checkout to commit financial operations through GetMyHotels, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`ref`	string	—	Hotel `ref` from `search_hotels` (e.g. 'TBO:1402689').
`price`	number	Yes	Total for the WHOLE stay (use `grandTotal` from `get_checkout_quote` verbatim — do not multiply it by the number of nights).
`rooms`	integer	—	Rooms (default 1).
`adults`	integer	—	Adults (default 2).
`checkIn`	string	Yes	Check-in date, ISO 8601.
`checkOut`	string	Yes	Check-out date, ISO 8601.
`children`	integer	—	Children (default 0).
`currency`	string	Yes	ISO 4217 currency (e.g. 'USD').
`roomName`	string	Yes	Room name.
`hotelName`	string	Yes	Hotel name.
`supplierCode`	string	—	Supplier code (if `ref` omitted).
`supplierRoomId`	string	Yes	Bookable room/rate id from `search_hotels`.

Parameters from the server's own tool schema.

RISK

Why create_one_click_checkout is rated Critical

Initiates a hotel payment checkout flow committing financial obligations for the user.

From the tool's definition Create a checkout... confirm + pay... saved card pre-selected

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_one_click_checkout 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 create_one_click_checkout, this is the rule to start with:

create_one_click_checkout Approval-gated

Any call to create_one_click_checkout is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_one_click_checkout": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect GetMyHotels, apply this rule, and every create_one_click_checkout call is checked against it from then on.

FAQ

Questions about create_one_click_checkout

What does the create_one_click_checkout tool do? +

Create a checkout for the signed-in user with a saved card pre-selected, and return a getmyhotels.com URL where they confirm + pay in one click. Does NOT charge the card — the user confirms on the hosted page. Get the savedPaymentMethodPublicId from list_payment_methods. Confirm the hotel, room, dates, and price with the user first. It is categorised as a Financial tool in the GetMyHotels MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does create_one_click_checkout accept? +

create_one_click_checkout accepts 12 parameters: ref, price, rooms, adults, checkIn, checkOut, children, currency, roomName, hotelName, supplierCode, supplierRoomId. Required: price, checkIn, checkOut, currency, roomName, hotelName, supplierRoomId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_one_click_checkout? +

Register the GetMyHotels MCP server in PolicyLayer and add a rule for create_one_click_checkout: 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.

What risk level is create_one_click_checkout? +

create_one_click_checkout is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit create_one_click_checkout? +

Yes. Add a rate_limit block to the create_one_click_checkout 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.

How do I block create_one_click_checkout completely? +

Set action: deny in the PolicyLayer policy for create_one_click_checkout. 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.

What MCP server provides create_one_click_checkout? +

create_one_click_checkout 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.

KEEP EXPLORING

More on GetMyHotels, and thousands of servers like it.

This server

All 18 GetMyHotels tools → Critical-risk tools on this server →

Across the catalogue

fundos_create_capital_call on Fundos →create_payment on Shopmonkey MCP Server →create_agent on Conviction →bank_transaction_create on AbraFlexi → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →