move_file

Move or rename a file or folder to a new location.

SERVERIconnect SOURCEiconnect-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-heznpc-iconnect/move-file.md

WHAT IT DOES

What move_file does on Iconnect

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

RISK

Why move_file is rated Medium

move_file performs Write-category operations: it modifies file/folder metadata and locations. Although move operations are technically reversible (files can be moved back), the high severity reflects the risk that an AI agent could move critical system files, application files, or user data to unexpected locations, causing application failures, data loss visibility, or system instability.

From the tool's definition Tool description states 'Move or rename a file or folder to a new location.' This is a reversible file system operation that modifies the state of the filesystem by changing file/folder locations and names.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_file, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every move_file call is checked against it from then on.

FAQ

Questions about move_file

What does the move_file tool do? +

Move or rename a file or folder to a new location. It is categorised as a Write tool in the Iconnect 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 Iconnect 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 Iconnect. 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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Iconnect, and thousands of servers like it.

This server

All 279 Iconnect tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →