fill_merge_fields

Fill merge fields in a document with provided data.

SERVERDocx SOURCEandrew82106/llm_docx_agent_mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/andrew82106-llm-docx-agent-mcp/fill-merge-fields.md

WHAT IT DOES

What fill_merge_fields does on Docx

AI agents use fill_merge_fields 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 fill_merge_fields is rated Medium

This tool modifies document content reversibly by substituting merge field placeholders with user-provided data. It creates or updates the visible/usable content of a document without permanently deleting or corrupting it, and does not execute arbitrary code or move money.

From the tool's definition Tool name 'fill_merge_fields' and description 'Fill merge fields in a document with provided data' indicate modification of document content by populating placeholders with supplied values.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

fill_merge_fields Rate-limited

fill_merge_fields 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": {
    "fill_merge_fields": {
      "limits": [
        {
          "counter": "fill_merge_fields_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 fill_merge_fields call is checked against it from then on.

FAQ

Questions about fill_merge_fields

What does the fill_merge_fields tool do? +

Fill merge fields in a document with provided data. 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 fill_merge_fields? +

Register the Docx MCP server in PolicyLayer and add a rule for fill_merge_fields: 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 fill_merge_fields? +

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

Can I rate-limit fill_merge_fields? +

Yes. Add a rate_limit block to the fill_merge_fields 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 fill_merge_fields completely? +

Set action: deny in the PolicyLayer policy for fill_merge_fields. 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 fill_merge_fields? +

fill_merge_fields 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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 24 Docx tools →

Across the catalogue

The MCP Attack Database →

Guides

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