This record as markdown: /tools/securityronin-docx-mcp/add-page-break.md
What add_page_break does on Docx
AI agents use add_page_break 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 add_page_break is rated Medium
Adding a page break modifies the document structure but is a reversible operation—the page break can be removed without data loss. This falls clearly under Write (creates/modifies data reversibly) rather than Execute or Destructive. The severity is low because the blast radius of inserting unwanted page breaks in a document is limited; the document remains readable and the change is easily undone.
From the tool's definition Tool name 'add_page_break' and description 'Insert a page break after a paragraph' indicate creation of a formatting element within the document. The verb 'Insert' is characteristic of Write operations that create or modify content reversibly.
Attacks that exploit this kind of access
The rule that runs add_page_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 add_page_break, this is the rule to start with:
add_page_break 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every add_page_break call is checked against it from then on.
Questions about add_page_break
Insert a page break after 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.
Register the Docx MCP server in PolicyLayer and add a rule for add_page_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.
add_page_break is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_page_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.
Set action: deny in the PolicyLayer policy for add_page_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.
add_page_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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue