move_directory · LocalFS MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_directory does on LocalFS MCP Server

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

WHY IT NEEDS A POLICY

Why move_directory needs a policy

Moving/renaming directories modifies the filesystem structure but is fundamentally reversible—the data and directory structure remain intact and can be restored. This distinguishes it from Destructive actions like delete_directory which removes data.

From the tool's definition Tool description states 'Move or rename a directory from source to destination path'. The operation is reversible via moving back to original path or via undo operations in typical filesystem contexts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_directory Rate-limited

move_directory 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_directory": {
      "limits": [
        {
          "counter": "move_directory_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 LocalFS MCP Server, so you can run agents against it safely.

FAQ

Questions about move_directory

What does the move_directory tool do? +

Move or rename a directory from source to destination path. It is categorised as a Write tool in the LocalFS 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_directory? +

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

What risk level is move_directory? +

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

Can I rate-limit move_directory? +

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

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

move_directory is provided by the LocalFS MCP Server MCP server (mcp-bridge/local-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

move_directory is one line of LocalFS MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →