This record as markdown: /tools/securityronin-docx-mcp/scrub-pii.md
What scrub_pii does on Docx
AI agents call scrub_pii 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 scrub_pii is rated Critical
'Scrubbing' PII typically means permanently removing or overwriting sensitive personal data from documents, which is an irreversible destructive operation. Given the server context (Word document manipulation at OOXML level), this likely modifies document content by permanently deleting PII fields. Confidence is reduced due to the empty description, but the name strongly implies destructive data removal.
From the tool's definition Tool name 'scrub_pii' implies irreversible removal of personally identifiable information from documents. The description is empty, providing no additional context.
Attacks that exploit this kind of access
The rule that runs scrub_pii 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 scrub_pii, this is the rule to start with:
scrub_pii 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 scrub_pii call is checked against it from then on.
Questions about scrub_pii
scrub_pii 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.
Register the Docx MCP server in PolicyLayer and add a rule for scrub_pii: 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.
scrub_pii 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 scrub_pii 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 scrub_pii. 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.
scrub_pii 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