This record as markdown: /tools/deep-ai-kr-dev-mcp/move-file.md
What move_file does on Dev
AI agents use move_file to create or update resources in Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dev environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | Source path (relative to root) |
destination | string | — | Destination path (relative to root) |
Parameters from the server's own tool schema.
Why move_file is rated Medium
Moving or renaming files modifies their paths and metadata but does not destroy data or create new persistent state that cannot be undone. The action is reversible (files can be moved back, renamed again), making it a Write operation rather than Destructive.
From the tool's definition Tool description states 'Move or rename a file or directory' — these are reversible modifications of file metadata and location.
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 Dev, 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 Dev, apply this rule, and every move_file call is checked against it from then on.
Questions about move_file
Move or rename a file or directory. It is categorised as a Write tool in the Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
move_file accepts 2 parameters: source, destination. The full parameter table on this page comes from the server's own tool schema.
Register the Dev 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 Dev. 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 Dev MCP server (deep-ai-kr/dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dev, and thousands of servers like it.
This server
Across the catalogue