Deep-copy a table row and insert the copy immediately after it.
AI agents use duplicate_table_row 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 modifies a document by adding a new row (copying an existing one), which is reversible and classifies as Write. The operation has low blast radius since duplicating table rows is a benign content modification with no destructive, financial, or code execution implications. No data loss or irreversible changes occur.
From the tool's definition Tool description states 'Deep-copy a table row and insert the copy immediately after it' — creates new content (a duplicated row) within a document without deleting or overwriting existing data.
Documented attack patterns abuse exactly the kind of access duplicate_table_row 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 duplicate_table_row:
{
"version": "1",
"default": "deny",
"tools": {
"duplicate_table_row": {
"limits": [
{
"counter": "duplicate_table_row_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}duplicate_table_row 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 row and insert the copy immediately after it. 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 duplicate_table_row: 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.
duplicate_table_row 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 duplicate_table_row 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 duplicate_table_row. 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.
duplicate_table_row 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.