copyFile
Creates a copy of a Google Drive file or document
This record as markdown: /tools/ark7-google-drive-mcp/copyfile.md
What copyFile does on Google Drive
AI agents use copyFile 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 |
|---|---|---|---|
fileId | string | Yes | ID of the file to copy |
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 |
newName | string | — | Name for the copied file. If not provided, will use 'Copy of [original name]' |
parentFolderId | string | — | ID or path of the destination folder (defaults to same folder as original) |
Parameters from the server's own tool schema.
Why copyFile is rated Medium
This tool creates new data (a file copy) reversibly without deleting or destroying anything. It is not destructive because the original remains intact and the action is reversible (the copy can be deleted). It does not execute arbitrary code or trigger external side effects beyond file duplication.
From the tool's definition Tool name is 'copyFile' and description states it 'Creates a copy of a Google Drive file or document' — explicitly a creation/write operation that modifies the state of Google Drive by adding a new resource.
Attacks that exploit this kind of access
The rule that runs copyFile 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 copyFile, this is the rule to start with:
copyFile 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 copyFile call is checked against it from then on.
Questions about copyFile
Creates a copy of a Google Drive file or document. 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.
copyFile accepts 4 parameters: fileId, account, newName, parentFolderId. Required: fileId. 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 copyFile: 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.
copyFile 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 copyFile 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 copyFile. 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.
copyFile 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