Critical Risk →

files.move

Move or rename files and folders. Supports batch operations for mass renaming. All paths must be under home directory.

How to control files.move ↓

What files.move does on Orchard

AI agents call files.move to permanently remove resources in Orchard — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why files.move needs a policy

Moving or renaming files/folders can be effectively irreversible — it changes the path and name of files, and batch operations amplify the blast radius significantly. If an AI agent misuses this tool, it could rename or relocate large numbers of files in ways that are difficult to recover from (especially without a backup), making data hard or impossible to find.

From the tool's definition Move or rename files and folders. Supports batch operations for mass renaming.

Documented attack patterns abuse exactly the kind of access files.move gives an agent:

How to control files.move

PolicyLayer is an MCP gateway — it sits between your AI agents and Orchard, and nothing reaches the server without passing your rules. This is the rule we recommend for files.move:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "files.move"
  ]
}

files.move disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Orchard — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about files.move

What does the files.move tool do? +

Move or rename files and folders. Supports batch operations for mass renaming. All paths must be under home directory. It is categorised as a Destructive tool in the Orchard MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

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

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

What risk level is files.move? +

files.move is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit files.move? +

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

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

files.move is provided by the Orchard MCP server (l22-io/orchard-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Orchard tool call.

Start from Orchard, 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.

65 Orchard tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.