move_file
Move or rename files and directories. Can move files between directories and rename them in a single operation. Both source and destination must be within allowed directories. ${PATH_GUIDANCE} ${CMD_PREFIX_DESCRIPTION}
This record as markdown: /tools/desktop-commander/move-file.md
What move_file does on Desktop Commander
AI agents use move_file to create or update resources in Desktop Commander, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Desktop Commander environment.
Why move_file is rated Medium
Moving and renaming files are write operations that modify file system metadata and organization reversibly. While the tool has significant blast radius (could reorganize critical system files if paths are misconfigured), the operations are not destructive (files are not deleted) and not permanent in the sense that moves can typically be undone.
From the tool's definition Tool description explicitly states 'Move or rename files and directories' and 'Can move files between directories and rename them in a single operation.' These are reversible modifications to file system state.
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 Desktop Commander, 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 Desktop Commander, 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. Both source and destination must be within allowed directories. ${PATH_GUIDANCE} ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Write tool in the Desktop Commander MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Desktop Commander 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 Desktop Commander. 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 Desktop Commander MCP server (wonderwhy-er/DesktopCommanderMCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander, and thousands of servers like it.
This server
Across the catalogue