This record as markdown: /tools/securityronin-docx-mcp/set-text-case.md
What set_text_case does on Docx
AI agents use set_text_case 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_text_case is rated Medium
This tool modifies document content by transforming the case (capitalization) of text within a run. While reversible through undo or reapplying the transformation, it is a write operation that alters the document state.
From the tool's definition Tool name 'set_text_case' and description 'Set text case transformation on a run' indicate modification of text formatting within a Word document run (a continuous sequence of text with consistent formatting).
Attacks that exploit this kind of access
The rule that runs set_text_case 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_text_case, this is the rule to start with:
set_text_case 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_text_case call is checked against it from then on.
Questions about set_text_case
Set text case transformation on a run. 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_text_case: 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_text_case 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_text_case 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_text_case. 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_text_case 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