merge_documents

Merge another DOCX document's content into the current document.

SERVERDocx SOURCEsecurityronin/docx-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/merge-documents.md

WHAT IT DOES

What merge_documents does on Docx

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.

RISK

Why merge_documents is rated Medium

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs merge_documents 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 merge_documents, this is the rule to start with:

merge_documents Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "merge_documents": {
      "limits": [
        {
          "counter": "merge_documents_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every merge_documents call is checked against it from then on.

FAQ

Questions about merge_documents

What does the merge_documents tool do? +

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.

How do I enforce a policy on merge_documents? +

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.

What risk level is merge_documents? +

merge_documents is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit merge_documents? +

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.

How do I block merge_documents completely? +

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.

What MCP server provides merge_documents? +

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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →