Medium Risk

move_file

Move or rename files and directories. Can move files between directories

How to control move_file ↓

What move_file does on Filesystem MCP Server for WSL

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

Medium Risk

Why move_file needs a policy

Moving or renaming files changes the filesystem structure and data organization, but the operation is reversible (a file can be moved back to its original location). This qualifies as Write rather than Destructive since no data is permanently lost.

From the tool's definition Tool is named 'move_file' and described as 'Move or rename files and directories. Can move files between directories.' This modifies the filesystem state by relocating files, which is a reversible operation.

Documented attack patterns abuse exactly the kind of access move_file gives an agent:

How to control move_file

PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem MCP Server for WSL, and nothing reaches the server without passing your rules. This is the rule we recommend for move_file:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_file": {
      "limits": [
        {
          "counter": "move_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Filesystem MCP Server for WSL — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about move_file

What does the move_file tool do? +

Move or rename files and directories. Can move files between directories. It is categorised as a Write tool in the Filesystem MCP Server for WSL 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 Filesystem MCP Server for WSL 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 Filesystem MCP Server for WSL. 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 Filesystem MCP Server for WSL MCP server (webconsulting/mcp-server-wsl-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem MCP Server for WSL tool call.

Start from Filesystem MCP Server for WSL, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

14 Filesystem MCP Server for WSL tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.