fs_move

A write tool on the Container- MCP server.

SERVERContainer-MCP SOURCE54rt1n/container-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/54rt1n-container-mcp/fs-move.md

WHAT IT DOES

What fs_move does on Container-MCP

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

RISK

Why fs_move is rated Medium

fs_move relocates or renames files, which constitutes data modification. While technically reversible (files can be moved back), it alters the file system structure and could disrupt application state if an AI agent moves critical files to wrong locations. This is less severe than Destructive (irreversible deletion) but more impactful than simple Read operations.

From the tool's definition Tool name 'fs_move' indicates file system movement/renaming operation. Sibling tools include fs_delete (destructive), fs_write (write), fs_read (read), suggesting this server manages file operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fs_move safely

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

fs_move Rate-limited

fs_move 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": {
    "fs_move": {
      "limits": [
        {
          "counter": "fs_move_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 Container-MCP, apply this rule, and every fs_move call is checked against it from then on.

FAQ

Questions about fs_move

What does the fs_move tool do? +

fs_move is a write tool on the Container MCP server. It is categorised as a Write tool in the Container-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 fs_move? +

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

What risk level is fs_move? +

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

Can I rate-limit fs_move? +

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

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

fs_move is provided by the Container MCP server (54rt1n/container-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Container, and thousands of servers like it.

This server

All 27 Container tools →

Across the catalogue

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

Guides

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