restore_from_trash
Restore a file from the trash to its original location (use the Key from list_trash)
This record as markdown: /tools/aiquila-nextcloud-mcp-server/restore-from-trash.md
What restore_from_trash does on AIquila — Nextcloud MCP Server
AI agents use restore_from_trash to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
Why restore_from_trash is rated Medium
Restoring files from trash creates or modifies the state of the file system (reinstatement of a deleted file in its original location). While reversible (the file can be deleted again), this is a data modification operation. It does not permanently destroy data (Destructive), does not run arbitrary code (Execute), and does not retrieve data without side effects (Read).
From the tool's definition Tool description states 'Restore a file from the trash to its original location' — this modifies the file system state by moving a file from trash back to its original location, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs restore_from_trash 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 restore_from_trash, this is the rule to start with:
restore_from_trash stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every restore_from_trash call is checked against it from then on.
Questions about restore_from_trash
Restore a file from the trash to its original location (use the Key from list_trash). It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for restore_from_trash: 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.
restore_from_trash is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the restore_from_trash 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 restore_from_trash. 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.
restore_from_trash 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.
This server
Across the catalogue