request_booking_action_code
Email a 6-digit verification code to the booking owner, required before cancelling or modifying a booking. Step 1 of 2 — then call cancel_booking/modify_booking with the code.
This record as markdown: /tools/com-getmyhotels-getmyhotels/request-booking-action-code.md
What request_booking_action_code does on GetMyHotels
AI agents use request_booking_action_code to create or update resources in GetMyHotels, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GetMyHotels environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | Which action the code authorizes. |
publicId | string | Yes | The booking's public id. |
Parameters from the server's own tool schema.
Why request_booking_action_code is rated Medium
Sends a verification email; no data modified, but enables destructive follow-up actions.
From the tool's definition Email a 6-digit verification code to the booking owner
Attacks that exploit this kind of access
The rule that runs request_booking_action_code 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 request_booking_action_code, this is the rule to start with:
request_booking_action_code 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 GetMyHotels, apply this rule, and every request_booking_action_code call is checked against it from then on.
Questions about request_booking_action_code
Email a 6-digit verification code to the booking owner, required before cancelling or modifying a booking. Step 1 of 2 — then call cancel_booking/modify_booking with the code. It is categorised as a Write tool in the GetMyHotels MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
request_booking_action_code accepts 2 parameters: action, publicId. Required: action, publicId. 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 request_booking_action_code: 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.
request_booking_action_code 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 request_booking_action_code 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 request_booking_action_code. 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.
request_booking_action_code 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