bulk_file_operations
Execute multiple file operations (move, copy, delete) sequentially in a single call. Returns per-item results.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/bulk-file-operations.md
What bulk_file_operations does on AIquila — Nextcloud MCP Server
AI agents call bulk_file_operations to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why bulk_file_operations is rated Critical
Although the tool also handles reversible operations (move, copy), the inclusion of delete functionality makes it Destructive per the rule that the most severe applicable category takes precedence. The bulk nature amplifies risk—a single malformed call could delete multiple files irreversibly.
From the tool's definition Tool explicitly permits "delete" operations as part of bulk file operations, which irreversibly removes data. Description states it executes "multiple file operations (move, copy, delete) sequentially."
Attacks that exploit this kind of access
The rule that runs bulk_file_operations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_file_operations, this is the rule to start with:
bulk_file_operations 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 AIquila — Nextcloud MCP Server, apply this rule, and every bulk_file_operations call is checked against it from then on.
Questions about bulk_file_operations
Execute multiple file operations (move, copy, delete) sequentially in a single call. Returns per-item results. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for bulk_file_operations: 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 AIquila — Nextcloud MCP Server. Nothing to install.
bulk_file_operations 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_file_operations 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_file_operations. 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_file_operations is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
Across the catalogue