Start an interactive Booking.com login. Opens a VISIBLE browser window at the sign-in page and returns
AI agents invoke booking_login to trigger actions in MCP Booking. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers browser automation to open a visible browser window and navigate to a login page. It executes an external browser action whose effects depend on subsequent interactions. It is not merely reading data — it initiates an interactive session that could lead to authenticated access enabling booking, cancellation, and financial transactions on Booking.com.
From the tool's definition Opens a VISIBLE browser window at the sign-in page
Attacks that exploit this kind of access
Start an interactive Booking.com login. Opens a VISIBLE browser window at the sign-in page and returns. It is categorised as a Execute tool in the MCP Booking MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Booking MCP server in PolicyLayer and add a rule for booking_login: 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_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the booking_login 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_login. 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_login 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 →