drive_restore
Restore a drive to a prior version (commits a new version; nothing is lost).
This record as markdown: /tools/ai-dataecho-mcp/drive-restore.md
What drive_restore does on Mcp
AI agents use drive_restore to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
drive | string | Yes | Drive name or drv_… id |
versionId | string | Yes | dv_… id from drive_history |
Parameters from the server's own tool schema.
Why drive_restore is rated Medium
This tool creates or modifies data reversibly by restoring a prior version and committing it as a new version. While it changes state, the operation is reversible (prior versions remain accessible) and does not permanently delete data. This qualifies as Write rather than Destructive.
From the tool's definition The tool description states 'Restore a drive to a prior version (commits a new version; nothing is lost).' This operation modifies the state of a drive by reverting it to a prior version, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs drive_restore safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_restore, this is the rule to start with:
drive_restore 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 Mcp, apply this rule, and every drive_restore call is checked against it from then on.
Questions about drive_restore
Restore a drive to a prior version (commits a new version; nothing is lost). It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
drive_restore accepts 2 parameters: drive, versionId. Required: drive, versionId. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for drive_restore: 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 Mcp. Nothing to install.
drive_restore 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 drive_restore 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 drive_restore. 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.
drive_restore is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue