cancel_booking
Cancel a scheduled booking by id (from list_bookings), optionally with a reason. Idempotent: cancelling an already-cancelled booking is a no-op.
This record as markdown: /tools/ai-featureboard-featureboard/cancel-booking.md
What cancel_booking does on FeatureBoard
AI agents call cancel_booking to permanently remove resources in FeatureBoard, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_booking is rated Critical
Cancelling a booking is an irreversible action that removes a scheduled commitment. While the tool is described as idempotent (re-cancelling is a no-op), the initial cancellation itself cannot be undone — the booking slot is released and any associated reservations or commitments are terminated. This qualifies as Destructive due to the irreversible nature of the cancellation.
From the tool's definition Cancel a scheduled booking by id... cancelling an already-cancelled booking is a no-op
Attacks that exploit this kind of access
The rule that runs cancel_booking safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_booking, this is the rule to start with:
cancel_booking is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every cancel_booking call is checked against it from then on.
Questions about cancel_booking
Cancel a scheduled booking by id (from list_bookings), optionally with a reason. Idempotent: cancelling an already-cancelled booking is a no-op. It is categorised as a Destructive tool in the FeatureBoard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FeatureBoard 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 FeatureBoard. 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 FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
Across the catalogue