hotel_details
Rich metadata (gallery, facilities, policies, per-room details) for a single hotel — called by the hotel widget on fullscreen open. Cost: 1 credit per call.
This record as markdown: /tools/com-gojinko-mcp-jinko/hotel-details.md
What hotel_details does on Jinko MCP
AI agents call hotel_details to retrieve information from Jinko MCP 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 |
|---|---|---|---|
checkin | string | — | Check-in date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the BFF. |
checkout | string | — | Check-out date (YYYY-MM-DD). Accepted for future cache-key alignment; currently unused by the BFF. |
hotel_id | string | Yes | Hotel ID (from a prior hotel_search offer). |
user_intent | string | — | A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used t |
Parameters from the server's own tool schema.
Why hotel_details is rated Low
This tool queries and returns hotel metadata in read-only fashion. It fetches information about a specific hotel (gallery images, facilities, policies, room details) but does not modify data, execute external operations, delete records, or commit financial transactions. The credit cost is a usage meter, not a financial transaction. Classification as Read is appropriate.
From the tool's definition Tool name 'hotel_details' and description 'Rich metadata (gallery, facilities, policies, per-room details) for a single hotel' indicate retrieval of hotel information with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs hotel_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jinko MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hotel_details, this is the rule to start with:
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 Jinko MCP, apply this rule, and every hotel_details call is checked against it from then on.
Questions about hotel_details
Rich metadata (gallery, facilities, policies, per-room details) for a single hotel — called by the hotel widget on fullscreen open. Cost: 1 credit per call. It is categorised as a Read tool in the Jinko MCP MCP Server, which means it retrieves data without modifying state.
hotel_details accepts 4 parameters: checkin, checkout, hotel_id, user_intent. Required: hotel_id. The full parameter table on this page comes from the server's own tool schema.
Register the Jinko MCP server in PolicyLayer and add a rule for 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 Jinko MCP. Nothing to install.
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 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 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.
hotel_details is provided by the Jinko MCP server (https://mcp.gojinko.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jinko, and thousands of servers like it.
This server
Across the catalogue