This record as markdown: /tools/securityronin-docx-mcp/add-content-control.md
What add_content_control does on Docx
AI agents use add_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 add_content_control is rated Medium
Content controls in Word are structural elements that modify document format and data binding but do not delete data or execute external code. This is a Write operation: reversible, creates or modifies document structure.
From the tool's definition Tool name 'add_content_control' combined with server's stated capability for 'editing... Microsoft Word documents' and 'OOXML-level document manipulation' indicates this adds content controls (structured data containers) to documents, a reversible…
Attacks that exploit this kind of access
The rule that runs add_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 add_content_control, this is the rule to start with:
add_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 add_content_control call is checked against it from then on.
Questions about add_content_control
add_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 add_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.
add_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 add_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 add_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.
add_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