Cancel a reservation on booboooking.com. Requires the reservation_id AND pin that were returned from the original booboooking_book call — both are needed as proof of booking ownership. If the user asks to cancel but you do not have the pin in your conversation state, you MUST ask them for it — yo...
Part of the booboooking Appointment Booking server.
Free to start. No card required.
AI agents may call booboooking_cancel to permanently remove or destroy resources in booboooking Appointment Booking. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call booboooking_cancel in a loop, permanently destroying resources in booboooking Appointment Booking. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"booboooking_cancel"
]
} See the full booboooking Appointment Booking policy for all 6 tools.
These attack patterns abuse exactly the kind of access booboooking_cancel gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Cancel a reservation on booboooking.com. Requires the reservation_id AND pin that were returned from the original booboooking_book call — both are needed as proof of booking ownership. If the user asks to cancel but you do not have the pin in your conversation state, you MUST ask them for it — you cannot cancel without it. Never invent or guess a pin.. It is categorised as a Destructive tool in the booboooking Appointment Booking MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the booboooking Appointment Booking MCP server in PolicyLayer and add a rule for booboooking_cancel: 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 booboooking Appointment Booking. Nothing to install.
booboooking_cancel 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 booboooking_cancel 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 booboooking_cancel. 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.
booboooking_cancel is provided by the booboooking Appointment Booking MCP server (https://booboooking.com/api/slot/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 booboooking Appointment Booking tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.