move_file · MCP File Operations Server MCP: Risk & Policy

WHAT IT DOES

What move_file does on MCP File Operations Server

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

WHY IT NEEDS A POLICY

Why move_file needs a policy

Moving/renaming files creates persistent changes to the file system structure that are reversible (files can be moved back). This is less severe than deletion (Destructive) but more severe than simple reads. The high severity reflects that careless use could reorganize critical files or overwrite destinations, causing operational disruption, though the operation itself is not irreversible like deletion.

From the tool's definition Tool description states 'Move/rename a file from source to destination' - this modifies file locations and names, which are reversible write operations. The requirement for 'write permission' confirms it performs data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_file Rate-limited

move_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_file": {
      "limits": [
        {
          "counter": "move_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 MCP File Operations Server, so you can run agents against it safely.

FAQ

Questions about move_file

What does the move_file tool do? +

Move/rename a file from source to destination (requires write permission). It is categorised as a Write tool in the MCP File Operations Server 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_file? +

Register the MCP File Operations Server MCP server in PolicyLayer and add a rule for move_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 MCP File Operations Server. Nothing to install.

What risk level is move_file? +

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

Can I rate-limit move_file? +

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

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

move_file is provided by the MCP File Operations Server MCP server (kavishankarks/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.