restore_file_version
Restore a previous version of a file (creates a new current version from the old one)
This record as markdown: /tools/aiquila-nextcloud-mcp-server/restore-file-version.md
What restore_file_version does on AIquila — Nextcloud MCP Server
AI agents use restore_file_version 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileId | number | Yes | The Nextcloud internal file ID |
versionId | string | Yes | The version identifier (from list_file_versions output) |
Parameters from the server's own tool schema.
Why restore_file_version is rated Medium
This tool modifies file data by restoring an older version as the current version. While it doesn't delete the old version or destroy data irreversibly, it does overwrite the current file state, making it a Write operation.
From the tool's definition Tool description states it 'Restore a previous version of a file (creates a new current version from the old one)' — this creates/modifies file content by reverting to a prior state.
Attacks that exploit this kind of access
The rule that runs restore_file_version 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_file_version, this is the rule to start with:
restore_file_version 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_file_version call is checked against it from then on.
Questions about restore_file_version
Restore a previous version of a file (creates a new current version from the old one). 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.
restore_file_version accepts 2 parameters: fileId, versionId. Required: fileId, versionId. 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 restore_file_version: 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_file_version 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_file_version 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_file_version. 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_file_version 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