Deep-copy a table and insert the copy immediately after the original.
AI agents use copy_table 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.
The tool performs a reversible modification: it creates a new copy of an existing table and inserts it into the document. This is a Write operation because it adds/modifies document content without permanently destroying data. While it changes the document structure, the operation can be undone (via undo/delete).
From the tool's definition Tool description states 'Deep-copy a table and insert the copy immediately after the original' — this creates new content (a duplicated table) within the document, modifying its structure and content.
Documented attack patterns abuse exactly the kind of access copy_table 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_table:
{
"version": "1",
"default": "deny",
"tools": {
"copy_table": {
"limits": [
{
"counter": "copy_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}copy_table 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.
Deep-copy a table and insert the copy immediately after the original. 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_table: 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_table 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_table 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_table. 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_table 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.