remove_bookmark

Remove a bookmark by name (keeps paragraph content).

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-bookmark.md

WHAT IT DOES

What remove_bookmark does on Docx

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

Removing a bookmark is an irreversible deletion of a document element. While the paragraph content is preserved, the bookmark itself cannot be recovered without an undo operation, making this Destructive. Severity is medium since it affects a discrete named element rather than bulk document content.

From the tool's definition 'Remove a bookmark by name' — permanently removes a named bookmark from the document

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remove_bookmark Hidden

remove_bookmark 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_bookmark"
  ]
}

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_bookmark call is checked against it from then on.

FAQ

Questions about remove_bookmark

What does the remove_bookmark tool do? +

Remove a bookmark by name (keeps paragraph content). 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_bookmark? +

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

remove_bookmark 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_bookmark? +

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

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

remove_bookmark 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 →