Medium Risk

set_run_size

Set the font size of a specific run in a paragraph.

How to control set_run_size ↓

What set_run_size does on Docx

AI agents use set_run_size 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.

Medium Risk

Why set_run_size needs a policy

This tool creates or modifies document data (font size properties) reversibly, which aligns with the Write category. While document formatting changes are non-destructive and can be undone, they do represent modification of the document state.

From the tool's definition Tool description states 'Set the font size of a specific run in a paragraph.' This modifies document formatting properties. Server description confirms 'editing...Microsoft Word documents' and 'OOXML-level document manipulation'.

Documented attack patterns abuse exactly the kind of access set_run_size gives an agent:

How to control set_run_size

PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for set_run_size:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_run_size": {
      "limits": [
        {
          "counter": "set_run_size_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Docx — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_run_size

What does the set_run_size tool do? +

Set the font size of 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_size? +

Register the Docx MCP server in PolicyLayer and add a rule for set_run_size: 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_size? +

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

Can I rate-limit set_run_size? +

Yes. Add a rate_limit block to the set_run_size 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_size completely? +

Set action: deny in the PolicyLayer policy for set_run_size. 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_size? +

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

Enforce policy on every Docx tool call.

Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.