Cancel a hotel reservation. This action cannot be undone. Requires guest first name, last name, and hotel confirmation number. Cancellation of non-refundable rates forfeits the full amount. The guest should be aware of the cancellation policy before this tool is called. To change dates: the recom...
Part of the 1stay server.
Free to start. No card required.
AI agents may call cancel_booking to permanently remove or destroy resources in 1stay. 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 cancel_booking in a loop, permanently destroying resources in 1stay. 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": [
"cancel_booking"
]
}See the full 1stay policy for all 8 tools.
These attack patterns abuse exactly the kind of access cancel_booking 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 hotel reservation. This action cannot be undone. Requires guest first name, last name, and hotel confirmation number. Cancellation of non-refundable rates forfeits the full amount. The guest should be aware of the cancellation policy before this tool is called. To change dates: the recommended pattern is to search and book new dates first, then cancel the original reservation. Canceling before securing a new booking risks losing the room. Cancellation confirmation is emailed to the address on file.. It is categorised as a Destructive tool in the 1stay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 1stay MCP server in PolicyLayer and add a rule for cancel_booking: 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 1stay. Nothing to install.
cancel_booking 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 cancel_booking 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 cancel_booking. 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.
cancel_booking is provided by the 1stay MCP server (https://mcp.stayker.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 1stay 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.