Raw hotel-ID lookup by city code and dates (lower-level than SEARCH_HOTELS; no live pricing).
AI agents call SEARCH_HOTEL_CITIES to retrieve information from Travel Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
SEARCH_HOTEL_CITIES retrieves hotel information by city code and dates but does not modify data, execute commands, delete records, or process payments. It is explicitly described as lower-level lookup with no pricing computation, making it a pure data retrieval tool with minimal blast radius if misused—an agent could only retrieve irrelevant hotel IDs, not cause harm.
From the tool's definition Tool performs a 'lookup' and retrieval operation with 'no live pricing', indicating read-only query functionality without modification or execution of external operations.
Attacks that exploit this kind of access
Raw hotel-ID lookup by city code and dates (lower-level than SEARCH_HOTELS; no live pricing). It is categorised as a Read tool in the Travel Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for SEARCH_HOTEL_CITIES: 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 Travel Agent MCP Server. Nothing to install.
SEARCH_HOTEL_CITIES 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_HOTEL_CITIES 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_HOTEL_CITIES. 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_HOTEL_CITIES is provided by the Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). 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 →