update_fields

Mark all fields as dirty so Word recalculates on open.

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/update-fields.md

WHAT IT DOES

What update_fields does on Docx

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

This tool modifies the state of fields within a Word document by flagging them for recalculation. It is a reversible write operation that changes document metadata/state rather than deleting data or executing arbitrary code. The blast radius is medium since it affects the entire document's fields, but it doesn't irreversibly destroy data.

From the tool's definition Mark all fields as dirty so Word recalculates on open

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_fields Rate-limited

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

FAQ

Questions about update_fields

What does the update_fields tool do? +

Mark all fields as dirty so Word recalculates on open. 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 update_fields? +

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

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

Can I rate-limit update_fields? +

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

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

update_fields 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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