move_project_file · Openl MCP: Risk & Policy

WHAT IT DOES

What move_project_file does on Openl

AI agents use move_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 move_project_file needs a policy

This tool modifies project structure by moving/renaming files and deletes the source file. While the operation is reversible through version control (staging allows review before commit), it involves file deletion and structural changes to the project. It's Write rather than Destructive because the action is staged (not immediately committed) and can be reverted before the openl_save_project commit step.

From the tool's definition Move or rename a file within a project. Maps to POST /projects/{projectId}/file-move. The source file is deleted after the move. The move is staged in the working copy — commit it with openl_save_project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_project_file Rate-limited

move_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": {
    "move_project_file": {
      "limits": [
        {
          "counter": "move_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 move_project_file

What does the move_project_file tool do? +

Move or rename a file within a project. Maps to POST /projects/{projectId}/file-move. Intermediate destination folders are created automatically and the source file is deleted after the move. A destination collision fails with HTTP 409. The move 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 move_project_file? +

Register the Openl MCP server in PolicyLayer and add a rule for move_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 move_project_file? +

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

Can I rate-limit move_project_file? +

Yes. Add a rate_limit block to the move_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 move_project_file completely? +

Set action: deny in the PolicyLayer policy for move_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 move_project_file? +

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