Client-side filter over the most recent booking_search results by price, review score, star rating,
AI agents call booking_filter_results 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 retrieves and filters existing search results using faceted parameters (price, review score, star rating). It has no side effects, does not modify reservations or bookings, does not execute commands, and does not involve financial transactions. It is strictly a data retrieval and presentation operation, analogous to a search/list function.
From the tool's definition Tool description states it performs 'Client-side filter over the most recent booking_search results by price, review score, star rating' — a purely read operation that queries and filters already-retrieved data without modification, creation, or deletion.
Attacks that exploit this kind of access
Client-side filter over the most recent booking_search results by price, review score, star rating,. 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_filter_results: 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_filter_results 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_filter_results 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_filter_results. 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_filter_results 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 →