manage_comment
Manages comment threads via the Drive API. action=create adds a NEW comment (needs content; optional quoted_text cites a passage — the API cannot anchor a new comment to a live range, that anchor format is not public, so it appears at document level). action=reply adds a reply (needs comment_id +...
This record as markdown: /tools/a1-x-tech-mcp-google-docs/manage-comment.md
What manage_comment does on Mcp Google Docs
AI agents call manage_comment to permanently remove resources in Mcp Google Docs, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | What to do with the document's comments. |
content | string | — | create/reply: the comment text (plain text). Optional closing text for resolve/reopen. |
comment_id | string | — | reply/resolve/reopen/delete: the comment thread to target (from list_comments). |
document_id | string | Yes | The document id — the long id from the document URL (docs.google.com/document/d/<documentId>/edit) or from create_document output. |
quoted_text | string | — | create only: the passage of document text the comment refers to (shown as a quote). |
Parameters from the server's own tool schema.
Why manage_comment is rated Critical
An AI agent that decides to call manage_comment doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Docs is gone. There is no undo for destructive operations.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs manage_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_comment, this is the rule to start with:
manage_comment 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 Mcp Google Docs, apply this rule, and every manage_comment call is checked against it from then on.
Questions about manage_comment
Manages comment threads via the Drive API. action=create adds a NEW comment (needs content; optional quoted_text cites a passage — the API cannot anchor a new comment to a live range, that anchor format is not public, so it appears at document level). action=reply adds a reply (needs comment_id + content). action=resolve closes the thread (needs comment_id; optional content posts a closing reply); action=reopen reactivates it. action=delete PERMANENTLY removes the comment and all its replies (needs comment_id) — deleting is final, resolving is the reversible way to close a thread. Get comment_id from list_comments. Requires a Drive scope on the OAuth token. It is categorised as a Destructive tool in the Mcp Google Docs MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
manage_comment accepts 5 parameters: action, content, comment_id, document_id, quoted_text. Required: action, document_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Docs MCP server in PolicyLayer and add a rule for manage_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 Mcp Google Docs. Nothing to install.
manage_comment 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 manage_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.
Set action: deny in the PolicyLayer policy for manage_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.
manage_comment is provided by the Mcp Google Docs MCP server (@a1-x-tech/mcp-google-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Docs, and thousands of servers like it.
Across the catalogue