move-document

Move a document to a new location

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-dev/move-document.md

WHAT IT DOES

What move-document does on Mcp Dev

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

RISK

Why move-document is rated Medium

Moving a document modifies its location/hierarchy within the content tree, which is a reversible change. While this could have significant impact on site structure and content organization (justifying 'high' severity due to potential for widespread disruption if misapplied to many documents), it is not destructive (data is not deleted), not financial, and does not execute arbitrary code.

From the tool's definition Tool name is 'move-document' and description states 'Move a document to a new location'. This performs a reversible relocation operation on content within Umbraco CMS.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move-document safely

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

move-document Rate-limited

move-document 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": {
    "move-document": {
      "limits": [
        {
          "counter": "move-document_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 Mcp Dev, apply this rule, and every move-document call is checked against it from then on.

FAQ

Questions about move-document

What does the move-document tool do? +

Move a document to a new location. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move-document? +

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

What risk level is move-document? +

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

Can I rate-limit move-document? +

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

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

move-document is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Dev, and thousands of servers like it.

This server

All 419 Mcp Dev tools →

Across the catalogue

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

Guides

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