Cancel a booking. Disabled unless write tools are explicitly enabled.
AI agents call golfbox_cancel_booking to permanently remove resources in GolfBox MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Canceling a booking destroys or voids a confirmed reservation that cannot be automatically restored without manual intervention. While not a permanent data deletion in the database sense, it irreversibly changes the state of a business commitment and makes the tee time available to others. This is more severe than Write (which is reversible via update) and qualifies as Destructive.
From the tool's definition Tool name is 'golfbox_cancel_booking' and description states it 'Cancel[s] a booking.' Cancellation is an irreversible action that removes/voids an existing reservation.
Attacks that exploit this kind of access
Cancel a booking. Disabled unless write tools are explicitly enabled. It is categorised as a Destructive tool in the GolfBox MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GolfBox MCP server in PolicyLayer and add a rule for golfbox_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 GolfBox MCP. Nothing to install.
golfbox_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 golfbox_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 golfbox_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.
golfbox_cancel_booking is provided by the GolfBox MCP server (j4hr3n/golfbox-mcp). 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 →