Save a complete snapshot of the open document to a new path.
AI agents use copy_document to create or update resources in Docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.
This tool creates new data (a document copy) reversibly without destroying the original or executing arbitrary code. While it writes to the filesystem, it does not execute external commands, delete data, or commit financial transactions.
From the tool's definition Tool creates a new document file by copying the currently open document to a new path. The description explicitly states 'Save a complete snapshot of the open document to a new path', indicating file creation/duplication rather than reading or destructive…
Documented attack patterns abuse exactly the kind of access copy_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for copy_document:
{
"version": "1",
"default": "deny",
"tools": {
"copy_document": {
"limits": [
{
"counter": "copy_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Save a complete snapshot of the open document to a new path. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx 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 Docx. 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 Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Docx, 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.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.