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.
AI agents use move_file to create or update resources in Wuying AgentBay — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wuying AgentBay environment.
This tool modifies file system state by relocating or renaming files, which is a reversible write operation. It is not destructive because files are not deleted—they are repositioned. It is not Execute because it does not run code or trigger external operations.
From the tool's definition Tool description: 'Move or rename files and directories. Can move files between directories and rename them in a single operation.' The operation is reversible (files can be moved back, renamed again), and does not permanently delete data.
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 Wuying AgentBay, 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.
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. It is categorised as a Write tool in the Wuying AgentBay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wuying AgentBay 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 Wuying AgentBay. 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 Wuying AgentBay MCP server (michael98671/agentbay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wuying AgentBay, 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.
59 Wuying AgentBay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.