Move or rename a file or directory.
AI agents use move_path to create or update resources in Filesystem MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filesystem MCP Server environment.
This tool modifies data by changing file/directory locations and names, which is characteristic of Write operations. While the filesystem is altered, the operation is reversible (the item can be moved back). This is less severe than Destructive (which permanently removes data) but more severe than Read.
From the tool's definition The tool description states "Move or rename a file or directory." Moving/renaming are reversible write operations that modify filesystem state without permanent data loss.
Attacks that exploit this kind of access
Move or rename a file or directory. It is categorised as a Write tool in the Filesystem MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem MCP Server MCP server in PolicyLayer and add a rule for move_path: 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 MCP Server. Nothing to install.
move_path 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_path 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_path. 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_path is provided by the Filesystem MCP Server MCP server (njbrake/filesystem-mcp-server). 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 →