Critical Risk →

floyd_cancel_booking

Cancel a held or confirmed booking. Releases the time slot.

Part of the Floyd server.

floyd_cancel_booking can permanently delete data in Floyd, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FLOYD →

Free to start. No card required.

AI agents may call floyd_cancel_booking to permanently remove or destroy resources in Floyd. 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 floyd_cancel_booking in a loop, permanently destroying resources in Floyd. 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "floyd_cancel_booking"
  ]
}

See the full Floyd policy for all 5 tools.

Get this rule live on your own Floyd server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FLOYD →

These attack patterns abuse exactly the kind of access floyd_cancel_booking gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so floyd_cancel_booking only ever does what you allow.

SECURE FLOYD →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the floyd_cancel_booking tool do? +

Cancel a held or confirmed booking. Releases the time slot.. It is categorised as a Destructive tool in the Floyd MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on floyd_cancel_booking? +

Register the Floyd MCP server in PolicyLayer and add a rule for floyd_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 Floyd. Nothing to install.

What risk level is floyd_cancel_booking? +

floyd_cancel_booking is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit floyd_cancel_booking? +

Yes. Add a rate_limit block to the floyd_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.

How do I block floyd_cancel_booking completely? +

Set action: deny in the PolicyLayer policy for floyd_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.

What MCP server provides floyd_cancel_booking? +

floyd_cancel_booking is provided by the Floyd MCP server (floyd/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Floyd tool call.

Deterministic rules across all 5 Floyd 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.