Merge another DOCX document's content into the current document.
AI agents use merge_documents 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 merge_documents tool modifies an existing document by inserting content from another document. This is a Write operation because it creates or modifies data reversibly (the merge can be undone via standard document operations like Ctrl+Z or by removing the merged content). It is not Destructive because the operation is reversible and does not permanently delete data.
From the tool's definition Tool description states it 'Merge[s] another DOCX document's content into the current document' — this is a reversible modification operation that combines documents by inserting content.
Documented attack patterns abuse exactly the kind of access merge_documents 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 merge_documents:
{
"version": "1",
"default": "deny",
"tools": {
"merge_documents": {
"limits": [
{
"counter": "merge_documents_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_documents 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.
Merge another DOCX document's content into the current document. 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 merge_documents: 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.
merge_documents 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 merge_documents 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 merge_documents. 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.
merge_documents 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.