AI agents use restore-file-version to create or update resources in Nextcloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nextcloud environment.
This tool creates or modifies data reversibly. Restoring a previous file version overwrites the current file content, which is a Write operation. The severity is medium because while the action is reversible (the current version typically remains in history), an agent could misuse this to restore outdated or malicious versions of critical files, potentially causing data integrity issues or service disruption.
From the tool's definition restore-file-version: tool restores a specific version of a file, which modifies the current state of the file by overwriting it with a previous version.
Attacks that exploit this kind of access
Restore a specific version of a file. It is categorised as a Write tool in the Nextcloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nextcloud 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 Nextcloud. 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 Nextcloud MCP server (nextcloud-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →