manage_comments
Comment threads on the presentation file (served by the Drive API internally — scoped to this one file, no generic Drive access). action=list returns comments with replies and resolved status (pageSize/page_token to paginate, include_deleted for tombstones); get needs comment_id; create needs con...
This record as markdown: /tools/a1-x-tech-mcp-google-slides/manage-comments.md
What manage_comments does on Mcp Google Slides
AI agents call manage_comments to permanently remove resources in Mcp Google Slides, 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 presentation's comments. |
content | string | — | create/reply: the comment text (plain text). |
resolve | boolean | — | reply only: also mark the whole thread resolved. |
page_size | integer | — | list: comments per page (1-100). |
comment_id | string | — | get/reply/delete: the comment id from list. |
page_token | string | — | list: nextPageToken from the previous page. |
include_deleted | boolean | — | list: include deleted comments as tombstones. |
presentation_id | string | Yes | The presentation id — the long id from the URL (docs.google.com/presentation/d/<presentationId>/edit) or from create_presentation output. |
Parameters from the server's own tool schema.
Why manage_comments is rated Critical
Delete action permanently removes comment threads and all replies, irreversibly.
From the tool's definition delete needs comment_id and permanently removes the thread with all replies
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 Slides, 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 Slides, apply this rule, and every manage_comments call is checked against it from then on.
Questions about manage_comments
Comment threads on the presentation file (served by the Drive API internally — scoped to this one file, no generic Drive access). action=list returns comments with replies and resolved status (pageSize/page_token to paginate, include_deleted for tombstones); get needs comment_id; create needs content and starts a new unanchored thread (the API cannot anchor a new comment to a specific slide or shape); reply needs comment_id + content and/or resolve=true (resolve closes the thread); delete needs comment_id and permanently removes the thread with all replies. Requires a Drive scope on the OAuth token (https://www.googleapis.com/auth/drive) — a presentations-only token gets a 403 here. It is categorised as a Destructive tool in the Mcp Google Slides MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
manage_comments accepts 8 parameters: action, content, resolve, page_size, comment_id, page_token, include_deleted, presentation_id. Required: action, presentation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google Slides 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 Slides. 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 Slides MCP server (@a1-x-tech/mcp-google-slides). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Slides, and thousands of servers like it.
Across the catalogue