drive_restore

Restore a drive to a prior version (commits a new version; nothing is lost).

SERVERMcp SOURCEhttps://dataecho.ai/mcp
Medium RISK CLASS
Category Write
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about drive_restore

What does the drive_restore tool do? +

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.

What parameters does drive_restore accept? +

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.

How do I enforce a policy on drive_restore? +

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.

What risk level is drive_restore? +

drive_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit drive_restore? +

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.

How do I block drive_restore completely? +

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.

What MCP server provides drive_restore? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.