copy_file_or_directory · Project Creator MCP: Risk & Policy

WHAT IT DOES

What copy_file_or_directory does on Project Creator MCP

AI agents use copy_file_or_directory to create or update resources in Project Creator MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Creator MCP environment.

WHY IT NEEDS A POLICY

Why copy_file_or_directory needs a policy

Copying files or directories creates new data artifacts in the file system. This is a Write operation because it modifies the file system state reversibly—copied files can be deleted. It is not Destructive because the original files remain intact and the operation is undoable.

From the tool's definition Tool description states 'Copy a file or directory to a new location.' This creates new file/directory copies, which are reversible write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_file_or_directory Rate-limited

copy_file_or_directory 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_file_or_directory": {
      "limits": [
        {
          "counter": "copy_file_or_directory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Project Creator MCP, so you can run agents against it safely.

FAQ

Questions about copy_file_or_directory

What does the copy_file_or_directory tool do? +

Copy a file or directory to a new location. It is categorised as a Write tool in the Project Creator MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on copy_file_or_directory? +

Register the Project Creator MCP server in PolicyLayer and add a rule for copy_file_or_directory: 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 Project Creator MCP. Nothing to install.

What risk level is copy_file_or_directory? +

copy_file_or_directory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit copy_file_or_directory? +

Yes. Add a rate_limit block to the copy_file_or_directory 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.

How do I block copy_file_or_directory completely? +

Set action: deny in the PolicyLayer policy for copy_file_or_directory. 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.

What MCP server provides copy_file_or_directory? +

copy_file_or_directory is provided by the Project Creator MCP server (jackalterman/project-creator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.