modify_booking

SERVERGetMyHotels SOURCEhttps://mcp.getmyhotels.com

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-getmyhotels-getmyhotels/modify-booking.md

WHAT IT DOES

What modify_booking does on GetMyHotels

AI agents use modify_booking 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
`checkIn`	string	—	New check-in date, ISO 8601 (optional).
`checkOut`	string	—	New check-out date, ISO 8601 (optional).
`publicId`	string	Yes	The booking's public id.
`specialRequests`	string	—	New special requests (≤2000 chars, optional).
`verificationCode`	string	Yes	6-digit code from `request_booking_action_code`.

Parameters from the server's own tool schema.

RISK

Why modify_booking is rated Medium

This tool modifies existing bookings (dates, prices, confirmations) in a reversible manner. While it affects financial records (price changes), the primary action is data modification rather than money movement. The 'modify' operation is typical Write behavior.

From the tool's definition Tool description explicitly states it can "Change one of the signed-in user's bookings" and mentions modifying dates which "can shift the price and issue a new confirmation." The description indicates modifications are reversible through cancel-and-rebook…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

modify_booking Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "modify_booking": {
      "limits": [
        {
          "counter": "modify_booking_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about modify_booking

What does the modify_booking tool do? +

Change one of the signed-in user's bookings. Requires the 6-digit verificationCode from request_booking_action_code. Special-request edits always apply. A DATE change is pushed to the hotel supplier as a cancel-and-rebook at current availability, so it only works for suppliers that support amendment — for others (and when no room is available for the new dates) it returns an error asking you to cancel and rebook instead. A date change can shift the price and issue a new confirmation; the result's supplierModifyStatus says whether the supplier reservation was actually changed (modified), simulated (simulated), or the edit stayed local (local_only, e.g. special requests only). Never promise a date change went through unless supplierModifyStatus is modified or simulated. 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.

What parameters does modify_booking accept? +

modify_booking accepts 5 parameters: checkIn, checkOut, publicId, specialRequests, verificationCode. Required: publicId, verificationCode. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on modify_booking? +

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

What risk level is modify_booking? +

modify_booking is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit modify_booking? +

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

How do I block modify_booking completely? +

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

What MCP server provides modify_booking? +

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

KEEP EXPLORING

More on GetMyHotels, and thousands of servers like it.

This server

All 18 GetMyHotels tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →