copy-document
Copy a document to a new location. Returns the new document
This record as markdown: /tools/mcp-dev/copy-document.md
What copy-document does on Mcp Dev
AI agents use copy-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.
Why copy-document is rated Medium
Copying a document in Umbraco CMS creates new content but is reversible (the copy can be deleted). This is a Write operation rather than Execute because it doesn't run arbitrary code or trigger unpredictable external effects; it's a bounded, predictable data creation action.
From the tool's definition Tool description states 'Copy a document to a new location. Returns the new document' — copying creates a new document resource in the CMS, which is a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs copy-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 copy-document, this is the rule to start with:
copy-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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every copy-document call is checked against it from then on.
Questions about copy-document
Copy a document to a new location. Returns the new document. 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.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for copy-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.
copy-document 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 copy-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.
Set action: deny in the PolicyLayer policy for copy-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.
copy-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.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue