set_properties
Set core document properties. Empty string = unchanged.
This record as markdown: /tools/securityronin-docx-mcp/set-properties.md
What set_properties does on Docx
AI agents use set_properties 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_properties is rated Medium
This tool creates or modifies document properties (author, title, subject, etc.), which is a reversible write operation. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions.
From the tool's definition Tool name is 'set_properties' and description states 'Set core document properties', indicating it modifies document metadata/properties. The phrase 'Empty string = unchanged' confirms reversible modification behavior.
Attacks that exploit this kind of access
The rule that runs set_properties 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_properties, this is the rule to start with:
set_properties 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_properties call is checked against it from then on.
Questions about set_properties
Set core document properties. Empty string = unchanged. 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_properties: 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_properties 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_properties 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_properties. 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_properties 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