93 tools. 50 can modify or destroy data without limits.
9 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (box_collaboration_delete_tool, box_docgen_template_delete_tool, box_file_delete_tool) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (box_collaboration_file_group_by_group_id_tool, box_collaboration_file_user_by_user_id_tool, box_collaboration_file_user_by_user_login_tool) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (box_authorize_app_tool) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Box. 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 @box-community/mcp-server-box box_collaboration_delete_tool:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
box_collaboration_file_group_by_group_id_tool:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
box_ai_ask_file_multi_tool:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Box server exposes 9 destructive tools including box_collaboration_delete_tool, box_docgen_template_delete_tool, box_file_delete_tool. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Box server has 40 write tools including box_collaboration_file_group_by_group_id_tool, box_collaboration_file_user_by_user_id_tool, box_collaboration_file_user_by_user_login_tool. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
93 tools across 4 categories: Destructive, Execute, Read, Write. 43 are read-only. 50 can modify, create, or delete data.
One line change. Instead of running the Box server directly, prefix it with Intercept: intercept -c box.yaml -- npx -y @@box-community/mcp-server-box. Download a pre-built policy from policylayer.com/policies/box 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