Low Risk

get_runs

Get all runs in a paragraph with their formatting properties.

How to control get_runs ↓

What get_runs does on Docx

AI agents call get_runs to retrieve information from Docx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_runs needs a policy

This tool retrieves and returns formatting metadata about text runs (the smallest unit of text with uniform formatting in Word documents) within a paragraph. It performs no mutations, side effects, or external operations—purely a read operation to examine existing document properties.

From the tool's definition Tool name 'get_runs' and description 'Get all runs in a paragraph with their formatting properties' indicate a retrieval operation that queries document structure without modifying data.

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

How to control get_runs

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 get_runs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_runs": {}
  }
}

get_runs is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_runs

What does the get_runs tool do? +

Get all runs in a paragraph with their formatting properties. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_runs? +

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

get_runs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_runs? +

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

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

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