Copy a file to a new location
AI agents use copy_file to create or update resources in Mcp Google Drive — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Google Drive environment.
Copying a file creates new data in a new location, which is a reversible write operation. It is not destructive (original file remains), not financial, and not execute (doesn't run code). While copying could proliferate large files and impact storage, the operation is reversible and medium severity reflects realistic risk when an AI agent misuses file copying permissions.
From the tool's definition Tool name 'copy_file' and description 'Copy a file to a new location' indicate file creation/duplication. The server description confirms 'full CRUD operations' with 'create' as one capability.
Attacks that exploit this kind of access
Copy a file to a new location. It is categorised as a Write tool in the Mcp Google Drive MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Google Drive MCP server in PolicyLayer and add a rule for 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 Mcp Google Drive. Nothing to install.
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 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 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.
copy_file is provided by the Mcp Google Drive MCP server (longtran2404/mcp-google-drive). 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 →