Critical-risk tools in Box
9 of the 93 tools in Box are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
box_collaboration_delete_toolDestructive 5/5Remove a collaboration from a file or folder
-
box_docgen_template_delete_toolDestructive 4/5Remove a file as a DocGen template
-
box_file_delete_toolDestructive 5/5Permanently delete a file
-
box_folder_delete_toolDestructive 5/5Permanently delete a folder and all contents
-
box_metadata_delete_instance_on_file_toolDestructive 4/5Delete metadata instance from a file
-
box_shared_link_file_remove_toolDestructive 4/5Remove a shared link from a file
-
box_shared_link_folder_remove_toolDestructive 4/5Remove a shared link from a folder
-
box_task_remove_toolDestructive 4/5Remove a task from a file
-
box_web_link_delete_by_id_toolDestructive 4/5Delete a web link
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Box
Enforce policy on Box
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init