fs_move_file

Move/rename a file within the allowlist.

SERVERLocalAnt SOURCEyuga-hashimoto/localant

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/yuga-hashimoto-localant/fs-move-file.md

WHAT IT DOES

What fs_move_file does on LocalAnt

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

RISK

Why fs_move_file is rated Medium

Moving or renaming files modifies the filesystem state reversibly—the operation can be undone by moving the file back or restoring from backup. This is a Write operation rather than Destructive because the data itself is not deleted or overwritten, merely relocated.

From the tool's definition Tool name 'fs_move_file' and description 'Move/rename a file within the allowlist' indicate file modification operations that are reversible.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fs_move_file safely

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

fs_move_file Rate-limited

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

FAQ

Questions about fs_move_file

What does the fs_move_file tool do? +

Move/rename a file within the allowlist. It is categorised as a Write tool in the LocalAnt 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_file? +

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

What risk level is fs_move_file? +

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

Can I rate-limit fs_move_file? +

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

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

fs_move_file is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on LocalAnt, and thousands of servers like it.

This server

All 216 LocalAnt tools →

Across the catalogue

write_file on 0sec →move-task on Kanban MCP Server → The MCP Attack Database →

Guides

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