delete_section_break

A destructive tool on the Docx MCP server.

SERVERDocx SOURCEsecurityronin/docx-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/delete-section-break.md

WHAT IT DOES

What delete_section_break does on Docx

AI agents call delete_section_break to permanently remove resources in Docx, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_section_break is rated Critical

While the description is empty, the tool name 'delete_section_break' combined with the server's document manipulation capability clearly indicates an irreversible deletion action. Removing section breaks permanently alters document structure and formatting.

From the tool's definition Tool name 'delete_section_break' indicates irreversible deletion of document structure. The server description mentions 'editing' and 'OOXML-level document manipulation', and sibling tools include destructive operations (delete_table, delete_row implied by…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_section_break 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 delete_section_break, this is the rule to start with:

delete_section_break Hidden

delete_section_break is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_section_break"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every delete_section_break call is checked against it from then on.

FAQ

Questions about delete_section_break

What does the delete_section_break tool do? +

delete_section_break is a destructive tool on the Docx MCP server. It is categorised as a Destructive tool in the Docx MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_section_break? +

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

delete_section_break is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_section_break? +

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

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

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

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →