copy-element

Copy an element to a new location. Returns the new element

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/copy-element.md

WHAT IT DOES

What copy-element does on Mcp Dev

AI agents use copy-element 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 copy-element is rated Medium

This tool creates or modifies data reversibly by copying an element to a new location in the CMS hierarchy. It does not execute arbitrary code, delete data irreversibly, or move financial resources. The action is reversible (the copy can be deleted and the original remains intact), placing it squarely in the Write category.

From the tool's definition Tool name 'copy-element' and description 'Copy an element to a new location. Returns the new element' indicate data replication and relocation within Umbraco CMS, creating a new copy without deletion of the original.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs copy-element 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 copy-element, this is the rule to start with:

copy-element Rate-limited

copy-element 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": {
    "copy-element": {
      "limits": [
        {
          "counter": "copy-element_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 copy-element call is checked against it from then on.

FAQ

Questions about copy-element

What does the copy-element tool do? +

Copy an element to a new location. Returns the new element. 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 copy-element? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for copy-element: 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 copy-element? +

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

Can I rate-limit copy-element? +

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

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

copy-element 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

The MCP Attack Database →

Guides

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