5 tools. 1 can modify or destroy data without limits.
1 destructive tool with no built-in limits. Policy required.
Last updated:
Destructive tools (floyd_cancel_booking) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Intercept sits between your agent and Floyd. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @floyd/mcp-server floyd_cancel_booking:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
floyd_confirm_booking:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Floyd server exposes 1 destructive tools including floyd_cancel_booking. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
5 tools across 2 categories: Destructive, Read. 4 are read-only. 1 can modify, create, or delete data.
One line change. Instead of running the Floyd server directly, prefix it with Intercept: intercept -c floyd-mcp-server.yaml -- npx -y @floyd/mcp-server. Download a pre-built policy from policylayer.com/policies/floyd-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init