get_sections

THE RISK

Low Risk

Why get_sections needs a policy

This tool retrieves and enumerates structural information about document sections (properties such as margins, page orientation, headers/footers) without modifying, deleting, or executing operations. It is a pure read operation with no side effects on the document or external systems.

From the tool's definition Tool name 'get_sections' with description 'List all sections in the document with their properties' — uses 'List' and 'get', indicating data retrieval only.

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

POLICY

How to control get_sections

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_sections": {}
  }
}

get_sections is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Docx tools

Destructive delete_column_from_table Delete a column (0-based) from every row of a table. Destructive delete_comment Delete a comment and remove its range markers from the document. Destructive delete_content_control Remove an SDT content control wrapper, keeping its content in place. Destructive delete_custom_property Delete a custom document property by name. Destructive delete_endnote Delete an endnote and its in-body reference. Destructive delete_field Remove a complete complex field (begin through end runs) from the document. Destructive delete_footer Delete a footer by location: default, first, or even. Destructive delete_footnote Delete a footnote and its in-body reference.

All 219 Docx tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_sections

What does the get_sections tool do? +

List all sections in the document with their 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_sections? +

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

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

Can I rate-limit get_sections? +

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

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

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

CHECK YOUR STACK →