AI agents use move_file to create or update resources in MCP Filesystem Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Filesystem Server environment.
Moving or renaming files modifies filesystem state and can disrupt application logic, references, or data organization. While reversible (files are not deleted), the impact is significant enough to warrant 'high' severity due to potential operational disruption. This is Write rather than Destructive because the operation can be undone by moving files back.
From the tool's definition Tool performs 'move or rename files and directories' — a reversible modification operation that changes file location and names within the filesystem.
Documented attack patterns abuse exactly the kind of access move_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Filesystem Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_file:
{
"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.
Free to start. No card required.
Move or rename files and directories. It is categorised as a Write tool in the MCP Filesystem Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Filesystem Server 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 MCP Filesystem Server. Nothing to install.
move_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
move_file is provided by the MCP Filesystem Server MCP server (safurrier/mcp-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 MCP Filesystem Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
21 MCP Filesystem Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.