This record as markdown: /tools/andrew82106-llm-docx-agent-mcp/copy-docx.md
What copy_docx does on Docx
AI agents use copy_docx 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.
Why copy_docx is rated Medium
Copying a document creates a new file at a specified location, which is a write operation (data creation). This is reversible (the copy can be deleted) and has minimal blast radius. No data is deleted, executed, or financially committed. It falls clearly into the Write category with low severity since document duplication is a routine, safe operation with no destructive or executing side effects.
From the tool's definition Tool name 'copy_docx' and description 'Copy a Word document to a new location' indicate file duplication—a reversible write operation that creates new data without modifying the original.
Attacks that exploit this kind of access
The rule that runs copy_docx safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copy_docx, this is the rule to start with:
copy_docx 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 Docx, apply this rule, and every copy_docx call is checked against it from then on.
Questions about copy_docx
Copy a Word document to a new location. 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_docx: 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_docx 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_docx 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_docx. 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_docx is provided by the Docx MCP server (andrew82106/llm_docx_agent_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docx, and thousands of servers like it.
This server
Across the catalogue