cancel_booking
Cancel one of the signed-in user's bookings. Requires the 6-digit verificationCode from request_booking_action_code. This may be irreversible and can trigger a refund per policy.
This record as markdown: /tools/com-getmyhotels-getmyhotels/cancel-booking.md
What cancel_booking does on GetMyHotels
AI agents call cancel_booking to permanently remove resources in GetMyHotels, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | — | Optional cancellation reason (≤1000 chars). |
publicId | string | Yes | The booking's public id. |
verificationCode | string | Yes | 6-digit code from `request_booking_action_code`. |
Parameters from the server's own tool schema.
Why cancel_booking is rated Critical
Cancelling a booking is an irreversible destructive action that terminates a user's reservation and can affect financial obligations (refunds). While it involves financial consequences, the primary action is the irreversible destruction/cancellation of the booking record itself.
From the tool's definition Tool description explicitly states "Cancel one of the signed-in user's bookings" and notes "This may be irreversible and can trigger a refund per policy." The cancellation is an irreversible action that modifies financial state.
Attacks that exploit this kind of access
The rule that runs cancel_booking 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 cancel_booking, this is the rule to start with:
cancel_booking is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect GetMyHotels, apply this rule, and every cancel_booking call is checked against it from then on.
Questions about cancel_booking
Cancel one of the signed-in user's bookings. Requires the 6-digit verificationCode from request_booking_action_code. This may be irreversible and can trigger a refund per policy. It is categorised as a Destructive tool in the GetMyHotels MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_booking accepts 3 parameters: reason, publicId, verificationCode. Required: publicId, verificationCode. 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 cancel_booking: 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.
cancel_booking is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_booking 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 cancel_booking. 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.
cancel_booking 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.
Across the catalogue