list_my_bookings
List the signed-in user's hotel bookings.
This record as markdown: /tools/com-getmyhotels-getmyhotels/list-my-bookings.md
What list_my_bookings does on GetMyHotels
AI agents call list_my_bookings 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 |
|---|---|---|---|
page | integer | — | Page number (default 1). |
limit | integer | — | Page size (default 20). |
Parameters from the server's own tool schema.
Why list_my_bookings is rated Low
This tool retrieves and displays existing booking information for an authenticated user. It performs a query operation with no side effects, reversible actions, code execution, or financial impact. The blast radius of misuse is minimal—an attacker would gain visibility into a user's bookings but cannot modify, delete, or charge them.
From the tool's definition Tool name 'list_my_bookings' and description 'List the signed-in user's hotel bookings' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs list_my_bookings 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 list_my_bookings, this is the rule to start with:
list_my_bookings 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 list_my_bookings call is checked against it from then on.
Questions about list_my_bookings
List the signed-in user's hotel bookings. It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
list_my_bookings accepts 2 parameters: page, limit. 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 list_my_bookings: 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.
list_my_bookings 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 list_my_bookings 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 list_my_bookings. 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.
list_my_bookings 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