New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

set_run_strikethrough

Set strikethrough on a specific run in a paragraph.

SERVERDocx SOURCEsecurityronin/docx-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/set-run-strikethrough.md

What set_run_strikethrough does on Docx

AI agents use set_run_strikethrough 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_run_strikethrough is rated Medium

This tool modifies document formatting by applying strikethrough to text, which is a reversible change to document structure. It does not delete data, execute code, or create financial obligations. The scope is limited to visual formatting of a single text run, making it a Write operation with low severity—misuse would only affect formatting appearance, not cause data loss or unauthorized actions.

From the tool's definition Tool name 'set_run_strikethrough' and description 'Set strikethrough on a specific run in a paragraph' indicate modification of document formatting.

Questions about set_run_strikethrough

What does the set_run_strikethrough tool do? +

Set strikethrough on a specific run in a paragraph. 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.

How do I enforce a policy on set_run_strikethrough? +

Register the Docx MCP server in PolicyLayer and add a rule for set_run_strikethrough: 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.

What risk level is set_run_strikethrough? +

set_run_strikethrough is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_run_strikethrough? +

Yes. Add a rate_limit block to the set_run_strikethrough 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.

How do I block set_run_strikethrough completely? +

Set action: deny in the PolicyLayer policy for set_run_strikethrough. 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.

What MCP server provides set_run_strikethrough? +

set_run_strikethrough 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Docx's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.