get_hotel_details
Get full property details (description, amenities, photos, policies, location) for a hotel, identified by its ref from search_hotels (or its supplierCode + supplierHotelId).
This record as markdown: /tools/com-getmyhotels-getmyhotels/get-hotel-details.md
What get_hotel_details does on GetMyHotels
AI agents call get_hotel_details 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 |
|---|---|---|---|
ref | string | — | The hotel `ref` from search (e.g. 'tbo:1360717'). |
supplierCode | string | — | Alternative to `ref`: supplier code. |
supplierHotelId | string | — | Alternative to `ref`: supplier hotel id. |
Parameters from the server's own tool schema.
Why get_hotel_details is rated Low
This tool retrieves hotel information for display purposes. It has no side effects: it does not create, modify, delete, execute code, or process payments. The blast radius of misuse is minimal—an agent could only retrieve unnecessary hotel details, which poses no security or operational risk.
From the tool's definition Tool name 'get_hotel_details' and description 'Get full property details (description, amenities, photos, policies, location)' indicate a retrieval operation with no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
The rule that runs get_hotel_details 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_hotel_details, this is the rule to start with:
get_hotel_details 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_hotel_details call is checked against it from then on.
Questions about get_hotel_details
Get full property details (description, amenities, photos, policies, location) for a hotel, identified by its ref from search_hotels (or its supplierCode + supplierHotelId). It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
get_hotel_details accepts 3 parameters: ref, supplierCode, supplierHotelId. 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_hotel_details: 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_hotel_details 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_hotel_details 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_hotel_details. 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_hotel_details 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