Search for hotels and properties on Booking.com. Returns property names, ratings, prices, and availability indicators.
AI agents call booking_search to retrieve information from MCP Booking without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information (hotel listings, ratings, prices, availability) from Booking.com without creating, modifying, or deleting any data. It produces no side effects beyond fetching results. This is a classic Read operation. The low severity reflects that misuse would only expose hotel search data, not financial transactions or destructive actions.
From the tool's definition Tool description states it 'Search for hotels and properties' and 'Returns property names, ratings, prices, and availability indicators.' The word 'search' and 'returns' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search for hotels and properties on Booking.com. Returns property names, ratings, prices, and availability indicators. It is categorised as a Read tool in the MCP Booking MCP Server, which means it retrieves data without modifying state.
Register the MCP Booking MCP server in PolicyLayer and add a rule for booking_search: 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 MCP Booking. Nothing to install.
booking_search 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 booking_search 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 booking_search. 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.
booking_search is provided by the MCP Booking MCP server (markswendsen-code/mcp-booking). 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 →