Cancel a hotel booking using the cancellation UUID sent to the guest
AI agents call CANCEL_HOTEL_BOOKING to permanently remove resources in Travel Agent MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a hotel booking is an irreversible action — once cancelled, the reservation is gone and may not be recoverable (especially close to the check-in date), potentially resulting in loss of room availability, cancellation fees, or forfeiture of prepaid amounts. This fits the Destructive category as it permanently removes a booking record and cannot be undone.
From the tool's definition Cancel a hotel booking using the cancellation UUID sent to the guest
Attacks that exploit this kind of access
Cancel a hotel booking using the cancellation UUID sent to the guest. It is categorised as a Destructive tool in the Travel Agent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Travel Agent MCP Server MCP server in PolicyLayer and add a rule for CANCEL_HOTEL_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 Travel Agent MCP Server. Nothing to install.
CANCEL_HOTEL_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_HOTEL_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_HOTEL_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_HOTEL_BOOKING is provided by the Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). 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 →