flatten_document
Accept all tracked changes and remove all revision markup.
This record as markdown: /tools/securityronin-docx-mcp/flatten-document.md
What flatten_document does on Docx
AI agents call flatten_document 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.
Why flatten_document is rated Critical
This tool irreversibly removes all tracked changes and revision markup from a document. Once revision history is flattened, the change history cannot be recovered, making this a destructive operation. An AI agent misusing this tool could cause permanent loss of document audit trails and editorial history.
From the tool's definition Accept all tracked changes and remove all revision markup
Attacks that exploit this kind of access
The rule that runs flatten_document 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 flatten_document, this is the rule to start with:
flatten_document is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every flatten_document call is checked against it from then on.
Questions about flatten_document
Accept all tracked changes and remove all revision markup. 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.
Register the Docx MCP server in PolicyLayer and add a rule for flatten_document: 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.
flatten_document is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the flatten_document 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 flatten_document. 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.
flatten_document 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.
Across the catalogue