create_document_copy
AI agents use create_document_copy to create or update resources in Doc/docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc/docx environment.
The tool creates a copy of a document, which is a write operation that modifies state (new document instance) but is reversible. While the description is empty, the name and server context strongly suggest document creation. Classified as Write rather than Destructive since copying is non-destructive.
From the tool's definition Tool name 'create_document_copy' and context of sibling tools like 'create_document', 'add_paragraph', 'add_table' indicate document creation/modification capability. Server description states it enables 'create, edit, and manage docx files'.
Documented attack patterns abuse exactly the kind of access create_document_copy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc/docx, and nothing reaches the server without passing your rules. This is the rule we recommend for create_document_copy:
{
"version": "1",
"default": "deny",
"tools": {
"create_document_copy": {
"limits": [
{
"counter": "create_document_copy_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_document_copy 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.
create_document_copy. It is categorised as a Write tool in the Doc/docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc/docx MCP server in PolicyLayer and add a rule for create_document_copy: 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 Doc/docx. Nothing to install.
create_document_copy 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 create_document_copy 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 create_document_copy. 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.
create_document_copy is provided by the Doc/docx MCP server (meterlong/mcp-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Doc/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.
23 Doc/docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.