move_file
Move or rename files and directories. Can move files between directories and rename them in a single operation. If the destination exists, the operation will fail. Works across different directories and can be used for simple renaming within the same directory. Both source and destination must be...
This record as markdown: /tools/filesystem/move-file.md
What move_file does on Filesystem
AI agents use move_file to create or update resources in Filesystem, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filesystem environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | Yes | |
destination | string | Yes |
Parameters from the server's own tool schema.
Why move_file is rated Medium
The tool modifies file paths and locations but does not delete or irreversibly destroy data. Files can be moved back to their original locations, making this a Write operation rather than Destructive. The severity is medium because misuse could corrupt application state or file organization, but the impact is recoverable via a reverse move operation.
From the tool's definition Tool description states it can 'Move or rename files and directories' and 'move files between directories'. These are reversible modifications to file system state.
Risk signalsAccepts file system path (destination)
Attacks that exploit this kind of access
The rule that runs move_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Filesystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For move_file, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Filesystem, apply this rule, and every move_file call is checked against it from then on.
Questions about move_file
Move or rename files and directories. Can move files between directories and rename them in a single operation. If the destination exists, the operation will fail. Works across different directories and can be used for simple renaming within the same directory. Both source and destination must be within allowed directories. It is categorised as a Write tool in the Filesystem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
move_file accepts 2 parameters: source, destination. Required: source, destination. The full parameter table on this page comes from the server's own tool schema.
Register the Filesystem 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. 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 Filesystem MCP server (@modelcontextprotocol/server-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Filesystem, and thousands of servers like it.
This server
Across the catalogue