This record as markdown: /tools/ai-dataecho-mcp/drive-move-file.md
What drive_move_file does on Mcp
AI agents use drive_move_file 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 |
|---|---|---|---|
to | string | Yes | New path |
from | string | Yes | Current path |
drive | string | Yes | Drive name or drv_… id |
Parameters from the server's own tool schema.
Why drive_move_file is rated Medium
This tool modifies the state of files (their location and name) within a drive but does not delete or irreversibly destroy data. The action is reversible—files can be moved again or renamed back. It is Write rather than Destructive because the data itself is preserved and the operation can be undone.
From the tool's definition Tool name 'drive_move_file' and description 'Move/rename a file inside a drive' indicate modification of file metadata and location within a managed storage system.
Attacks that exploit this kind of access
The rule that runs drive_move_file 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_move_file, this is the rule to start with:
drive_move_file 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_move_file call is checked against it from then on.
Questions about drive_move_file
Move/rename a file inside a drive. 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_move_file accepts 3 parameters: to, from, drive. Required: to, from, drive. 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_move_file: 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_move_file 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_move_file 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_move_file. 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_move_file 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