bulk_delete_files
Soft-delete multiple files at once (max 100). Returns count of deleted files.
This record as markdown: /tools/cloud-easybits-easybits/bulk-delete-files.md
What bulk_delete_files does on EasyBits
AI agents call bulk_delete_files to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bulk_delete_files is rated Critical
Irreversibly removes files; bulk operation amplifies impact even if soft-deleted.
From the tool's definition delete multiple files at once, soft-delete
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_delete_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_delete_files, this is the rule to start with:
bulk_delete_files is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every bulk_delete_files call is checked against it from then on.
Questions about bulk_delete_files
Soft-delete multiple files at once (max 100). Returns count of deleted files. It is categorised as a Destructive tool in the EasyBits MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EasyBits MCP server in PolicyLayer and add a rule for bulk_delete_files: 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 EasyBits. Nothing to install.
bulk_delete_files is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the bulk_delete_files 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.
Set action: deny in the PolicyLayer policy for bulk_delete_files. 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.
bulk_delete_files is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue