Copy a file or directory. For multiple operations, use batch_copy_files.
AI agents use copy_file to create or update resources in OODA Computer Control — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OODA Computer Control environment.
Copying files creates new data copies on the system, which is a reversible write operation. It does not delete data (ruling out Destructive), execute arbitrary code (ruling out Execute), or move money (ruling out Financial). Severity is medium because uncontrolled file copying could consume disk space, create sensitive data duplicates, or aid in exfiltration, but the operation is reversible by deletion.
From the tool's definition Tool name 'copy_file' and description 'Copy a file or directory' indicate file creation/replication operations. The sibling tool 'batch_copy_files' confirms this is a write operation class.
Documented attack patterns abuse exactly the kind of access copy_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for copy_file:
{
"version": "1",
"default": "deny",
"tools": {
"copy_file": {
"limits": [
{
"counter": "copy_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Copy a file or directory. For multiple operations, use batch_copy_files. It is categorised as a Write tool in the OODA Computer Control MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OODA Computer Control 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 OODA Computer Control. 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 OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, 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.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.