get_my_booking
Get full details of one of the signed-in user's bookings by its public id.
This record as markdown: /tools/com-getmyhotels-getmyhotels/get-my-booking.md
What get_my_booking does on GetMyHotels
AI agents call get_my_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 |
|---|---|---|---|
publicId | string | Yes | The booking's public id. |
Parameters from the server's own tool schema.
Why get_my_booking is rated Low
This tool retrieves and displays existing booking data for an authenticated user. It has no side effects—it does not create, modify, delete, or process payments. The operation is clearly informational (Read category). Severity is low because exposure of this tool would only allow reading a user's own booking details, which poses minimal risk if properly scoped to authenticated users.
From the tool's definition Tool name and description both indicate a read-only operation: 'Get full details of one of the signed-in user's bookings by its public id.' This retrieves booking information without modification, deletion, or financial transaction.
Attacks that exploit this kind of access
The rule that runs get_my_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_my_booking, this is the rule to start with:
get_my_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_my_booking call is checked against it from then on.
Questions about get_my_booking
Get full details of one of the signed-in user's bookings by its public id. It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
get_my_booking accepts 1 parameter: publicId. Required: 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 get_my_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_my_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_my_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_my_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_my_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