This record as markdown: /tools/ark7-google-drive-mcp/moveitem.md
What moveItem does on Google Drive
AI agents use moveItem 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 |
|---|---|---|---|
itemId | string | Yes | ID of the item to move |
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 |
destinationFolderId | string | — | Destination folder ID |
Parameters from the server's own tool schema.
Why moveItem is rated Medium
moveItem is classified as Write rather than Destructive because moving is reversible — the user can move the item back to its original location. It is not Execute because it does not run code or trigger external operations based on arbitrary arguments.
From the tool's definition Tool description states 'Move a file or folder' — this modifies the hierarchical location of data within Google Drive. Moving is a reversible write operation that changes metadata (parent folder) but does not delete or create new data.
Attacks that exploit this kind of access
The rule that runs moveItem 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 moveItem, this is the rule to start with:
moveItem 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 moveItem call is checked against it from then on.
Questions about moveItem
Move a file or folder. 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.
moveItem accepts 3 parameters: itemId, account, destinationFolderId. Required: itemId. 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 moveItem: 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.
moveItem 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 moveItem 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 moveItem. 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.
moveItem 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