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.
| Parameter | Type | Required | Description |
|---|---|---|---|
operations | array | Yes | Array of file operations to execute sequentially |
Parameters from the server's own tool schema.
Why bulk_file_operations is rated Critical
While the tool also supports reversible operations (move, copy), it explicitly includes delete functionality which cannot be undone. The bulk nature of the operation amplifies the risk—a single misconfigured call could irreversibly remove multiple files. Per the classification rules, Destructive takes precedence over Write when both are present.
From the tool's definition Tool description states it can execute 'delete' operations as part of bulk file operations. The capability to delete files irreversibly, especially in bulk across multiple items in a single call, places this in the Destructive category.
Risk signalsAccepts file system path (operations[].destination)
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.
bulk_file_operations accepts 1 parameter: operations. Required: operations. The full parameter table on this page comes from the server's own tool schema.
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