Searches for accommodation options in a specified location
AI agents call get_accommodations to retrieve information from Server Travelplanner without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
budget | number | — | Maximum price per night |
checkIn | string | Yes | Check-in date (YYYY-MM-DD) |
checkOut | string | Yes | Check-out date (YYYY-MM-DD) |
location | string | Yes | Location to search |
Parameters from the server's own tool schema.
This tool performs a read-only search operation to retrieve accommodation information. It has no side effects—it queries a database or external service for existing accommodation data and returns results. The user specifies a location parameter, but the operation is purely informational with no capability to book, modify, or delete accommodations.
From the tool's definition Tool name 'get_accommodations' and description 'Searches for accommodation options in a specified location' indicate a query/search operation that retrieves data without modifying, deleting, or executing external actions.
Attacks that exploit this kind of access
Searches for accommodation options in a specified location. It is categorised as a Read tool in the Server Travelplanner MCP Server, which means it retrieves data without modifying state.
get_accommodations accepts 4 parameters: budget, checkIn, checkOut, location. Required: checkIn, checkOut, location. The full parameter table on this page comes from the server's own tool schema.
Register the Server Travelplanner MCP server in PolicyLayer and add a rule for get_accommodations: 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 Server Travelplanner. Nothing to install.
get_accommodations 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_accommodations 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_accommodations. 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_accommodations is provided by the Server Travelplanner MCP server (@gongrzhe/server-travelplanner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →