restoreRevision
Restore a file to a selected revision (creates a new head revision). Note: workspace files (Docs, Sheets, Slides) are restored via export/import and may lose some formatting.
This record as markdown: /tools/ark7-google-drive-mcp/restorerevision.md
What restoreRevision does on Google Drive
AI agents use restoreRevision to create or update resources in Google Drive, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Drive environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
fileId | string | Yes | Google Drive file ID |
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
confirm | boolean | — | Safety flag. Must be true to execute restore. |
revisionId | string | Yes | Revision ID to restore |
Parameters from the server's own tool schema.
Why restoreRevision is rated Medium
restoreRevision modifies file data reversibly by restoring a previous version. While it reverts content, the restoration itself is a write operation that creates a new revision rather than permanently destroying data. The high severity reflects that an AI agent could misuse this to overwrite important current work by restoring to an old revision.
From the tool's definition 'Restore a file to a selected revision (creates a new head revision)' - the tool modifies file content by reverting to a previous state and creating a new head revision, which is a write operation that changes the current state of the file.
Attacks that exploit this kind of access
The rule that runs restoreRevision safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For restoreRevision, this is the rule to start with:
restoreRevision 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 Google Drive, apply this rule, and every restoreRevision call is checked against it from then on.
Questions about restoreRevision
Restore a file to a selected revision (creates a new head revision). Note: workspace files (Docs, Sheets, Slides) are restored via export/import and may lose some formatting. It is categorised as a Write tool in the Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
restoreRevision accepts 4 parameters: fileId, account, confirm, revisionId. Required: fileId, revisionId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for restoreRevision: 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 Google Drive. Nothing to install.
restoreRevision 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 restoreRevision 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 restoreRevision. 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.
restoreRevision is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue