New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

files.move_file

Move a stored file to a new account-relative path. Pass source_file_name from files.list_uploaded_files and the desired destination_file_name. The file is copied to the new path and the source is removed. Any linked upload session is updated to the new path. Cost = 0 tokens.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp
Medium RISK CLASS
Category Write
Parameters 22 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/files.move-file.md

What files.move_file does on Vee3

AI agents use files.move_file to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.

ParameterTypeRequiredDescription
source_file_name string Yes Current relative file name or path. Use files.list_uploaded_files to see available names.
destination_file_name string Yes New relative file name or path. Must not already exist in account storage.

Parameters from the server's own tool schema.

Why files.move_file is rated Medium

Modifies file organization reversibly; source removal is non-destructive if destination succeeds.

From the tool's definition Move stored file to new path; file copied and source removed.

Questions about files.move_file

What does the files.move_file tool do? +

Move a stored file to a new account-relative path. Pass source_file_name from files.list_uploaded_files and the desired destination_file_name. The file is copied to the new path and the source is removed. Any linked upload session is updated to the new path. Cost = 0 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does files.move_file accept? +

files.move_file accepts 2 parameters: source_file_name, destination_file_name. Required: source_file_name, destination_file_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on files.move_file? +

Register the Vee3 MCP server in PolicyLayer and add a rule for files.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 Vee3. Nothing to install.

What risk level is files.move_file? +

files.move_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit files.move_file? +

Yes. Add a rate_limit block to the files.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.

How do I block files.move_file completely? +

Set action: deny in the PolicyLayer policy for files.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.

What MCP server provides files.move_file? +

files.move_file is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Vee3, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vee3's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.