remove_watermark

Remove VML watermarks (e.g., DRAFT) from all document headers.

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/remove-watermark.md

WHAT IT DOES

What remove_watermark does on Docx

AI agents call remove_watermark 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 remove_watermark is rated Critical

This tool irreversibly removes watermarks from all document headers. The action is destructive because it permanently deletes document elements (VML watermarks) across the entire document, with no indication of reversibility. Misuse could result in permanent loss of document markings such as DRAFT status indicators across all headers.

From the tool's definition Remove VML watermarks... from all document headers

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remove_watermark Hidden

remove_watermark 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": [
    "remove_watermark"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_watermark

What does the remove_watermark tool do? +

Remove VML watermarks (e.g., DRAFT) from all document headers. 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 remove_watermark? +

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

remove_watermark 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 remove_watermark? +

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

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

remove_watermark 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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →