Creates a copy of a Google Drive file or document.
AI agents use copyFile to create or update resources in Google Docs & Drive MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs & Drive MCP Server environment.
This tool creates new data (a duplicated file) in Google Drive, making it a Write operation. It is not destructive since the original file remains and the action is reversible (the copy can be deleted). Severity is medium because misuse could consume storage quota or create unwanted duplicates, but the impact is limited to the user's own Drive and reversal is straightforward.
From the tool's definition copyFile creates a copy of a Google Drive file or document, which is a reversible data modification operation that adds new data to the user's Drive storage.
Attacks that exploit this kind of access
Creates a copy of a Google Drive file or document. It is categorised as a Write tool in the Google Docs & Drive MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Docs & Drive MCP Server 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 Docs & Drive MCP Server. 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 Docs & Drive MCP Server MCP server (oregpt/agenticledger_mcp_docsonly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →