Relocate or rename files and directories in a single atomic operation.
AI agents use move_file to create or update resources in Vulcan File Ops — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vulcan File Ops environment.
move_file modifies file system state by changing file locations and names—a classic Write operation. It is reversible (files can be moved again to their original location), so it does not meet the Destructive threshold.
From the tool's definition Tool description states 'Relocate or rename files and directories in a single atomic operation.' The verb 'relocate' and 'rename' indicate modification of file metadata and placement, which are reversible operations.
Documented attack patterns abuse exactly the kind of access move_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vulcan File Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for move_file:
{
"version": "1",
"default": "deny",
"tools": {
"move_file": {
"limits": [
{
"counter": "move_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Relocate or rename files and directories in a single atomic operation. It is categorised as a Write tool in the Vulcan File Ops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vulcan File Ops 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 Vulcan File Ops. 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 Vulcan File Ops MCP server (n0zer0d4y/vulcan-file-ops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vulcan File Ops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Vulcan File Ops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.