Create a copy of a file in Google Drive. Args: - file_id (string): The ID of the file to copy - name (string, optional): New name for the copied file (defaults to
AI agents use drive_copy_file to create or update resources in Google Workspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace environment.
This tool creates a new file resource in Google Drive, which is a reversible write operation. It does not delete or overwrite existing data (Destructive), does not execute arbitrary code (Execute), does not involve financial transactions (Financial), and goes beyond simple data retrieval (Read).
From the tool's definition Tool name and description: 'drive_copy_file' - 'Create a copy of a file in Google Drive.' This creates new data (a duplicate file) in the user's storage.
Documented attack patterns abuse exactly the kind of access drive_copy_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for drive_copy_file:
{
"version": "1",
"default": "deny",
"tools": {
"drive_copy_file": {
"limits": [
{
"counter": "drive_copy_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} drive_copy_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.
Free to start. No card required.
Create a copy of a file in Google Drive. Args: - file_id (string): The ID of the file to copy - name (string, optional): New name for the copied file (defaults to. It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP server in PolicyLayer and add a rule for drive_copy_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 Google Workspace. Nothing to install.
drive_copy_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_copy_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_copy_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_copy_file is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.