move_files · System Information MCP Server MCP

WHAT IT DOES

What move_files does on System Information MCP Server

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

WHY IT NEEDS A POLICY

Why move_files needs a policy

Moving or renaming files modifies file system state reversibly—the operation can be undone by moving files back to original locations or renaming them again. This is a Write operation rather than Destructive (data is not deleted or overwritten). Severity is medium because misuse could disrupt system organization or application functionality, but the safety guards against critical directories reduce impact.

From the tool's definition Tool name 'move_files' and description 'Move or rename files/directories' indicate modification of filesystem metadata and location without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_files Rate-limited

move_files 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_files": {
      "limits": [
        {
          "counter": "move_files_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 System Information MCP Server, so you can run agents against it safely.

FAQ

Questions about move_files

What does the move_files tool do? +

Move or rename files/directories. It is categorised as a Write tool in the System Information MCP 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_files? +

Register the System Information MCP Server MCP server in PolicyLayer and add a rule for move_files: 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 System Information MCP Server. Nothing to install.

What risk level is move_files? +

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

Can I rate-limit move_files? +

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

Set action: deny in the PolicyLayer policy for move_files. 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_files? +

move_files is provided by the System Information MCP Server MCP server (markolive1501/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.