move_file · Vigentic MCP: Risk & Policy

WHAT IT DOES

What move_file does on Vigentic MCP

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

WHY IT NEEDS A POLICY

Why move_file needs a policy

This tool modifies filesystem state by relocating or renaming files. While theoretically reversible (a file can be moved back), the action irreversibly changes file paths and references, potentially breaking project structure, imports, and build configurations. In the context of an AI agent with filesystem access, this poses significant risk of unintended file organization damage.

From the tool's definition Tool name 'move_file' and description 'Move or rename a file on disk' indicates file system modification that is reversible through another move operation.

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 Vigentic MCP, so you can run agents against it safely.

FAQ

Questions about move_file

What does the move_file tool do? +

Move or rename a file on disk, reusing an open source buffer when possible. It is categorised as a Write tool in the Vigentic 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 move_file? +

Register the Vigentic 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 Vigentic MCP. 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 Vigentic MCP server (munozu/vigentic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.