list_merge_fields

Extract all MERGEFIELD names from a document or template.

SERVERDocx SOURCEandrew82106/llm_docx_agent_mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

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

WHAT IT DOES

What list_merge_fields does on Docx

AI agents call list_merge_fields to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_merge_fields is rated Low

This tool performs a read-only operation that extracts and returns information about merge fields present in a document. It has no side effects, does not modify data, and does not trigger external operations. It is purely informational and analogous to a search or list operation.

From the tool's definition Tool name 'list_merge_fields' and description 'Extract all MERGEFIELD names from a document or template' indicate a query operation that retrieves metadata about merge fields without modifying the document.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_merge_fields Allowed

list_merge_fields is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_merge_fields": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_merge_fields

What does the list_merge_fields tool do? +

Extract all MERGEFIELD names from a document or template. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_merge_fields? +

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

list_merge_fields is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_merge_fields? +

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

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

list_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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →