Copy a file from source to destination without passing content through the agent. If the destination file already exists, it will be overwritten. Both source and destination must be within allowed directories.
AI agents use copy_file to create or update resources in FilesystemMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FilesystemMCP environment.
The tool creates or overwrites files (Write category). It is reversible (can be undone by copying the original back or deleting), so it is not Destructive. Overwriting existing files without warning is a significant risk if an agent misuses the tool to overwrite critical configuration or data files.
From the tool's definition copy_file: 'Copy a file from source to destination without passing content through the agent. If the destination file already exists, it will be overwritten.' The tool modifies the filesystem by creating/overwriting files.
Attacks that exploit this kind of access
Copy a file from source to destination without passing content through the agent. If the destination file already exists, it will be overwritten. Both source and destination must be within allowed directories. It is categorised as a Write tool in the FilesystemMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem 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 FilesystemMCP. 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 Filesystem MCP server (rijadalisic/filesystemmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
copy_file is one line of Filesystem's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →