Clear saved Booking.com session and cookies. Use this to log out or reset authentication state.
AI agents call booking_logout to permanently remove resources in MCP Booking — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Logging out irreversibly destroys the current session and cookies. While no financial data or reservations are deleted, the authentication state is permanently cleared and cannot be undone without re-authenticating. This is closer to Destructive than Write since the session data is erased rather than modified.
From the tool's definition Clear saved Booking.com session and cookies. Use this to log out or reset authentication state.
Attacks that exploit this kind of access
Clear saved Booking.com session and cookies. Use this to log out or reset authentication state. It is categorised as a Destructive tool in the MCP Booking MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Booking MCP server in PolicyLayer and add a rule for booking_logout: 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_logout is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the booking_logout 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_logout. 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_logout 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 →