manage_comments
Manages Drive comments on a file (Docs, Sheets, Slides, PDFs, images...). action=list pages through comments with their replies and resolved state (page_token; include_deleted shows tombstones); get fetches one (needs comment_id). create adds a comment (needs content; quoted_text attaches the pas...
This record as markdown: /tools/a1-x-tech-mcp-google-drive/manage-comments.md
What manage_comments does on Mcp Google Drive
AI agents call manage_comments to permanently remove resources in Mcp Google Drive, 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 file's comments. |
anchor | string | — | create only: a Drive anchor JSON string for region-anchorable media (rarely needed). |
content | string | — | create/reply: the comment text (plain text). Optional closing note for resolve/reopen. |
file_id | string | Yes | The file id — the long id from the Drive URL (drive.google.com/file/d/<fileId> or docs.google.com/.../d/<fileId>/edit) or from search_files/get_file output. Fol |
page_size | integer | — | list: comments per page (1..100; API default 20). |
comment_id | string | — | get/reply/resolve/reopen/delete: the comment id (from action=list). |
page_token | string | — | list: nextPageToken from the previous page. |
quoted_text | string | — | create only: the file passage the comment refers to (shown as a quote; does not position the comment). |
include_deleted | boolean | — | list: include deleted comments as tombstones (default false). |
Parameters from the server's own tool schema.
Why manage_comments is rated Critical
An AI agent that decides to call manage_comments doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp Google Drive 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_comments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For manage_comments, this is the rule to start with:
manage_comments 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 Drive, apply this rule, and every manage_comments call is checked against it from then on.
Questions about manage_comments
Manages Drive comments on a file (Docs, Sheets, Slides, PDFs, images...). action=list pages through comments with their replies and resolved state (page_token; include_deleted shows tombstones); get fetches one (needs comment_id). create adds a comment (needs content; quoted_text attaches the passage it refers to — display only; positional anchoring inside a Doc's text is not possible through this API, such comments appear file-level). reply answers a thread (needs comment_id + content). resolve / reopen close or reopen a thread (need comment_id; optional content adds a closing note). delete removes a comment and its replies permanently (needs comment_id; author only). Comments carry author, createdTime/modifiedTime, resolved and quotedFileContent. Not for Docs suggestions — those are a Docs feature this API cannot touch. It is categorised as a Destructive tool in the Mcp Google Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
manage_comments accepts 9 parameters: action, anchor, content, file_id, page_size, comment_id, page_token, quoted_text, include_deleted. Required: action, file_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Drive MCP server in PolicyLayer and add a rule for manage_comments: 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 Drive. Nothing to install.
manage_comments 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_comments 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_comments. 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_comments is provided by the Mcp Google Drive MCP server (@a1-x-tech/mcp-google-drive). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Drive, and thousands of servers like it.
Across the catalogue