fetch
Fetch the full record for a result id returned by search (a hotel) or for a booking reference (prefixed 'bk_'). Returns a document with id, title, text, url, and metadata.
This record as markdown: /tools/com-getmyhotels-getmyhotels/fetch.md
What fetch does on GetMyHotels
AI agents call fetch 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 |
|---|---|---|---|
id | string | Yes | An id from `search` results, or a 'bk_'-prefixed booking ref. |
Parameters from the server's own tool schema.
Why fetch is rated Low
This tool retrieves hotel details or booking information by result/reference ID and returns data without modifying, deleting, or executing any actions. It is a straightforward data retrieval operation with no side effects. Given the hotel search context and sibling tools like get_hotel_details, get_booking, and get_my_booking which serve similar read purposes, fetch fits the Read category.
From the tool's definition Tool description states it 'Fetch[es] the full record' and 'Returns a document with id, title, text, url, and metadata.' The verb 'fetch' and the operation of retrieving and returning existing data with no modification capability indicates a read-only…
Attacks that exploit this kind of access
The rule that runs fetch 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 fetch, this is the rule to start with:
fetch 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 fetch call is checked against it from then on.
Questions about fetch
Fetch the full record for a result id returned by search (a hotel) or for a booking reference (prefixed 'bk_'). Returns a document with id, title, text, url, and metadata. It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
fetch accepts 1 parameter: id. Required: id. 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 fetch: 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.
fetch 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 fetch 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 fetch. 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.
fetch 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