get_booking
Look up a hotel booking by its management token (sent in the confirmation email). Returns the booking status, hotel, dates, and guest details.
This record as markdown: /tools/com-getmyhotels-getmyhotels/get-booking.md
What get_booking does on GetMyHotels
AI agents call get_booking 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 |
|---|---|---|---|
bookingToken | string | Yes | The booking management token from the confirmation email/URL. |
Parameters from the server's own tool schema.
Why get_booking is rated Low
This tool queries and retrieves existing booking information using a management token. It performs a lookup operation that returns data without creating, modifying, deleting, or executing any external operations. The action is purely informational, making it a Read category tool.
From the tool's definition Tool description states 'Look up a hotel booking' and 'Returns the booking status, hotel, dates, and guest details' — retrieval operations with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_booking, this is the rule to start with:
get_booking 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_booking call is checked against it from then on.
Questions about get_booking
Look up a hotel booking by its management token (sent in the confirmation email). Returns the booking status, hotel, dates, and guest details. It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
get_booking accepts 1 parameter: bookingToken. Required: bookingToken. 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_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.
get_booking 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_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 get_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.
get_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.
This server
Across the catalogue