get_booking_status
AI agents call get_booking_status to retrieve information from Lastminutedeals Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves booking status information without modifying, executing external operations, or creating financial obligations. It is a read-only query operation with minimal blast radius if misused by an AI agent—worst case being repeated queries or information disclosure about bookings the agent has access to.
From the tool's definition Tool name 'get_booking_status' indicates a status query operation. The sibling tools (book_from_itinerary, book_slot, create_stripe_checkout_sessions, preview_slot, search_slots) confirm this server handles booking workflows, and a 'get_' prefixed tool…
Attacks that exploit this kind of access
get_booking_status. It is categorised as a Read tool in the Lastminutedeals Api MCP Server, which means it retrieves data without modifying state.
Register the Lastminutedeals Api MCP server in PolicyLayer and add a rule for get_booking_status: 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 Lastminutedeals Api. Nothing to install.
get_booking_status 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_booking_status 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_booking_status. 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_booking_status is provided by the Lastminutedeals Api MCP server (johnanleitner1-Coder/lastminutedeals-api). 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 →