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...
AI agents use move_file to create or update resources in FilesystemMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FilesystemMCP environment.
Moving/renaming files modifies the filesystem state but is reversible—the file still exists and can be moved back or renamed again. This qualifies as Write rather than Destructive, since the data is not deleted or irreversibly overwritten. The tool's explicit check that 'if the destination exists, the operation will fail' further confirms it avoids destructive overwrites.
From the tool's definition Tool description explicitly states it 'Move or rename files and directories' and 'can move files between directories and rename them in a single operation.' These are reversible modifications to filesystem state.
Attacks that exploit this kind of access
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 FilesystemMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 FilesystemMCP. 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 (rijadalisic/filesystemmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →