search_hotels
Search live hotel availability for a destination and date range. Returns a price-sorted list of hotels (JSON in the text), each with a ref and its cheapest bookable room's supplierRoomId. To book: pass a room's supplierRoomId + the hotel ref to get_checkout_quote then create_checkout. For a hotel...
This record as markdown: /tools/com-getmyhotels-getmyhotels/search-hotels.md
What search_hotels does on GetMyHotels
AI agents call search_hotels 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 |
|---|---|---|---|
rooms | integer | — | Rooms (1-6). Default 1. |
adults | integer | — | Adults (1-10). Default 2. |
checkIn | string | Yes | Check-in date, ISO 8601 (YYYY-MM-DD). |
checkOut | string | Yes | Check-out date, ISO 8601 (YYYY-MM-DD). Must be after check-in. |
children | integer | — | Children (0-6). Default 0. |
keywords | string | — | Optional free-text preferences, e.g. 'beachfront pool spa'. |
destination | string | Yes | City, region, or place to search (e.g. 'Paris', 'Goa', 'Lower Manhattan'). |
childrenAges | array | — | Age of each child at check-in. Length should equal `children`. |
guestNationality | string | — | ISO 3166-1 alpha-2 guest nationality (e.g. 'US', 'GB'). Affects supplier pricing. |
Parameters from the server's own tool schema.
Why search_hotels is rated Low
search_hotels is a read-only operation that retrieves and queries hotel availability and pricing data. While it returns information used to facilitate bookings downstream, the tool itself performs no side effects—it does not create, modify, delete, or charge. The description explicitly indicates it searches and returns results without state changes. This is a standard read operation with low severity.
From the tool's definition Tool description states it 'Search[es] live hotel availability' and 'Returns a price-sorted list of hotels'. The function performs a search query with no modification of data, no execution of arbitrary operations, and no financial transactions.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs search_hotels 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 search_hotels, this is the rule to start with:
search_hotels 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 search_hotels call is checked against it from then on.
Questions about search_hotels
Search live hotel availability for a destination and date range. Returns a price-sorted list of hotels (JSON in the text), each with a ref and its cheapest bookable room's supplierRoomId. To book: pass a room's supplierRoomId + the hotel ref to get_checkout_quote then create_checkout. For a hotel's other rooms (or a hotel not in the list), call get_rooms. Narrow with keywords (a hotel name, area, or amenities). It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
search_hotels accepts 9 parameters: rooms, adults, checkIn, checkOut, children, keywords, destination, childrenAges, guestNationality. Required: checkIn, checkOut, destination. 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 search_hotels: 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.
search_hotels 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 search_hotels 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 search_hotels. 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.
search_hotels 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