copy_file
Copy a file to a new location. Supports binary files (DOCX, PDF, images, etc.) and preserves exact file content.
This record as markdown: /tools/cowork-os/copy-file.md
What copy_file does on CoWork OS
AI agents use copy_file to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why copy_file is rated Medium
This tool creates or duplicates data reversibly—a hallmark of Write operations. While it does not modify existing files in place, it does introduce new file artifacts into the filesystem. The severity is medium because uncontrolled copying could fill disk space, expose sensitive data to new locations, or clutter the filesystem; however, the original data remains and the action can be undone by deleting the copy.
From the tool's definition Tool name 'copy_file' and description explicitly states it 'Copy a file to a new location' and 'preserves exact file content.' This creates new data (a file copy) without deleting the original.
Attacks that exploit this kind of access
The rule that runs copy_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copy_file, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every copy_file call is checked against it from then on.
Questions about copy_file
Copy a file to a new location. Supports binary files (DOCX, PDF, images, etc.) and preserves exact file content. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS 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 CoWork OS. 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 CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue