This record as markdown: /tools/ark7-google-drive-mcp/listcomments.md
What listComments does on Google Drive
AI agents call listComments to retrieve information from Google Drive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
pageSize | number | — | Max comments to return (1-100, default: 100) |
pageToken | string | — | Token for next page of results |
documentId | string | Yes | The document ID |
includeDeleted | boolean | — | Whether to include deleted comments (default: false) |
Parameters from the server's own tool schema.
Why listComments is rated Low
The tool retrieves and displays existing comments without altering, creating, or removing them. This is a pure read operation with minimal blast radius. Even if an AI agent calls it repeatedly, the only effect is retrieving data that already exists.
From the tool's definition Tool name is 'listComments' and description states 'List all comments in a Google Document' — this is a query/retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs listComments safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listComments, this is the rule to start with:
listComments is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every listComments call is checked against it from then on.
Questions about listComments
List all comments in a Google Document. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
listComments accepts 5 parameters: account, pageSize, pageToken, documentId, includeDeleted. Required: documentId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for listComments: 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 Google Drive. Nothing to install.
listComments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listComments 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 listComments. 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.
listComments is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue