drive_history

Version timeline of a drive (every write is a restorable version).

SERVERMcp SOURCEhttps://dataecho.ai/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-dataecho-mcp/drive-history.md

WHAT IT DOES

What drive_history does on Mcp

AI agents call drive_history to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`drive`	string	Yes	Drive name or drv_… id

Parameters from the server's own tool schema.

RISK

Why drive_history is rated Low

This tool retrieves the version history of a drive, which is a read-only operation. It lists historical versions without modifying, deleting, or executing anything. The description explicitly focuses on viewing the timeline of versions, not restoring or altering them.

From the tool's definition Version timeline of a drive (every write is a restorable version)

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drive_history 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_history, this is the rule to start with:

drive_history Allowed

drive_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every drive_history call is checked against it from then on.

FAQ

Questions about drive_history

What does the drive_history tool do? +

Version timeline of a drive (every write is a restorable version). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does drive_history accept? +

drive_history accepts 1 parameter: drive. Required: drive. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on drive_history? +

Register the MCP server in PolicyLayer and add a rule for drive_history: 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_history? +

drive_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit drive_history? +

Yes. Add a rate_limit block to the drive_history 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_history completely? +

Set action: deny in the PolicyLayer policy for drive_history. 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_history? +

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 26 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →