sandbox_files_move

Move or rename a file/directory inside the sandbox. Parent directories of the destination are created if needed.

SERVEREasyBits SOURCE@easybits.cloud/mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/sandbox-files-move.md

WHAT IT DOES

What sandbox_files_move does on EasyBits

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

RISK

Why sandbox_files_move is rated Medium

Reversible file operation within sandbox; modifies directory structure but permits undo via counter-move.

From the tool's definition Move or rename a file/directory inside the sandbox.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sandbox_files_move safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_files_move, this is the rule to start with:

sandbox_files_move Rate-limited

sandbox_files_move 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sandbox_files_move": {
      "limits": [
        {
          "counter": "sandbox_files_move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every sandbox_files_move call is checked against it from then on.

FAQ

Questions about sandbox_files_move

What does the sandbox_files_move tool do? +

Move or rename a file/directory inside the sandbox. Parent directories of the destination are created if needed. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sandbox_files_move? +

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

What risk level is sandbox_files_move? +

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

Can I rate-limit sandbox_files_move? +

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

Set action: deny in the PolicyLayer policy for sandbox_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 sandbox_files_move? +

sandbox_files_move is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools →

Across the catalogue

move-task on Kanban MCP Server →scaffold_project_files on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →