Critical Risk →

box_file_delete_tool

Permanently delete a file

Risk signalsPermanently removes file from Box

Part of the Box server.

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

SECURE BOX →

Free to start. No card required.

AI agents may call box_file_delete_tool to permanently remove or destroy resources in Box. 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 box_file_delete_tool in a loop, permanently destroying resources in Box. 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": [
    "box_file_delete_tool"
  ]
}

See the full Box policy for all 93 tools.

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

ENFORCE ON MY BOX →

View all 93 tools →

These attack patterns abuse exactly the kind of access box_file_delete_tool 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 box_file_delete_tool only ever does what you allow.

SECURE BOX →

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

What does the box_file_delete_tool tool do? +

Permanently delete a file. It is categorised as a Destructive tool in the Box 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 box_file_delete_tool? +

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

What risk level is box_file_delete_tool? +

box_file_delete_tool 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 box_file_delete_tool? +

Yes. Add a rate_limit block to the box_file_delete_tool 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 box_file_delete_tool completely? +

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

box_file_delete_tool is provided by the Box MCP server (@box-community/mcp-server-box). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Box tool call.

Deterministic rules across all 93 Box 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.