set_document_protection
Set document protection. edit: trackedChanges/comments/readOnly/forms/none.
This record as markdown: /tools/securityronin-docx-mcp/set-document-protection.md
What set_document_protection does on Docx
AI agents use set_document_protection 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 set_document_protection is rated Medium
The tool creates or modifies document protection settings reversibly—protection can be added, removed, or changed. This is a Write operation (modification without deletion). Severity is medium because while it affects document security posture and could restrict legitimate access or hide modifications, the changes are reversible and don't destroy data or move money.
From the tool's definition Tool name 'set_document_protection' with description indicating it sets protection modes including 'trackedChanges/comments/readOnly/forms/none'. This modifies document metadata and access controls.
Attacks that exploit this kind of access
The rule that runs set_document_protection 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 set_document_protection, this is the rule to start with:
set_document_protection 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 set_document_protection call is checked against it from then on.
Questions about set_document_protection
Set document protection. edit: trackedChanges/comments/readOnly/forms/none. 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 set_document_protection: 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.
set_document_protection 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 set_document_protection 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 set_document_protection. 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.
set_document_protection 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