copy_project_file · Openl MCP: Risk & Policy

WHAT IT DOES

What copy_project_file does on Openl

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

WHY IT NEEDS A POLICY

Why copy_project_file needs a policy

The tool creates or duplicates data (a file copy) within a project, which is a reversible modification. It is not destructive because it does not delete or overwrite (the description explicitly notes 'There is NO overwrite option' and fails with HTTP 409 if destination exists). It does not execute arbitrary code or trigger external operations.

From the tool's definition Tool description states it 'Copy a file within a project to a new project-relative path' and 'The copy is staged in the working copy — commit it with openl_save_project'. This creates a new file object in the project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_project_file Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "copy_project_file": {
      "limits": [
        {
          "counter": "copy_project_file_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 Openl, so you can run agents against it safely.

FAQ

Questions about copy_project_file

What does the copy_project_file tool do? +

Copy a file within a project to a new project-relative path. Maps to POST /projects/{projectId}/file-copy. Intermediate destination folders are created automatically. There is NO overwrite option — if destinationPath already exists the call fails with HTTP 409; choose a different destination or delete the existing file first. The copy is staged in the working copy — commit it with openl_save_project. Use. It is categorised as a Write tool in the Openl 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_project_file? +

Register the Openl MCP server in PolicyLayer and add a rule for copy_project_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 Openl. Nothing to install.

What risk level is copy_project_file? +

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

Can I rate-limit copy_project_file? +

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

How do I block copy_project_file completely? +

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

What MCP server provides copy_project_file? +

copy_project_file is provided by the Openl MCP server (openl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.