This record as markdown: /tools/securityronin-docx-mcp/update-content-control.md
What update_content_control does on Docx
AI agents use update_content_control 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.
Why update_content_control is rated Medium
This tool modifies document elements (content controls) but does not delete data or trigger financial transactions. Content control updates in Word documents are reversible via undo/version history, placing it in the Write category. Severity is medium because misconfiguration could corrupt document structure or lock fields, but effects are generally recoverable.
From the tool's definition Tool name 'update_content_control' indicates modification of document content controls. Server description states it enables 'editing...Microsoft Word documents' and 'precise OOXML-level document manipulation.' Content control updates are reversible…
Attacks that exploit this kind of access
The rule that runs update_content_control 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_content_control, this is the rule to start with:
update_content_control 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every update_content_control call is checked against it from then on.
Questions about update_content_control
update_content_control is a write tool on the Docx MCP server. 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 update_content_control: 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.
update_content_control 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 update_content_control 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 update_content_control. 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.
update_content_control 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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue