resolve_comment

Mark a comment as resolved (sets w15:done='1' in commentsExtended.xml).

SERVERDocx SOURCEsecurityronin/docx-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/resolve-comment.md

WHAT IT DOES

What resolve_comment does on Docx

AI agents use resolve_comment 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.

RISK

Why resolve_comment is rated Medium

This is a reversible modification of comment metadata, not deletion or structural destruction. Resolving/unresolving comments is a normal document workflow action with minimal blast radius. An agent misusing this would only toggle comment resolution flags, causing minor inconvenience but no data loss or external side effects.

From the tool's definition "Mark a comment as resolved" is a metadata state change on an existing comment element (setting w15:done='1' in commentsExtended.xml). The operation modifies document state but does not create, delete, or destroy content—it updates an attribute flag.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resolve_comment Rate-limited

resolve_comment 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_comment": {
      "limits": [
        {
          "counter": "resolve_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about resolve_comment

What does the resolve_comment tool do? +

Mark a comment as resolved (sets w15:done='1' in commentsExtended.xml). 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.

How do I enforce a policy on resolve_comment? +

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

resolve_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_comment? +

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

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

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

Across the catalogue

resolve_circuit on 0gzk → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →