List comments on a Google Doc. Args: - file_id (string): The ID of the Google Doc - include_deleted (boolean): Include deleted comments (default: false) - page_size (number): Max comments to return, 1-100 (default: 20) - page_token (string, optional): Pagination token for next page - response_for...
AI agents call drive_list_comments to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing comments on a document without creating, modifying, or deleting data. It has no side effects beyond returning information. The inclusion of 'include_deleted' is a filter option, not a restoration or modification capability. This is a straightforward Read operation with minimal blast radius if misused—an AI agent could only access comments it has permission to view.
From the tool's definition Tool name 'drive_list_comments' and description 'List comments on a Google Doc' indicates a retrieval operation with no modification capabilities.
Documented attack patterns abuse exactly the kind of access drive_list_comments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for drive_list_comments:
{
"version": "1",
"default": "deny",
"tools": {
"drive_list_comments": {}
}
} drive_list_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List comments on a Google Doc. Args: - file_id (string): The ID of the Google Doc - include_deleted (boolean): Include deleted comments (default: false) - page_size (number): Max comments to return, 1-100 (default: 20) - page_token (string, optional): Pagination token for next page - response_format (. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for drive_list_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 Google Workspace. Nothing to install.
drive_list_comments 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 drive_list_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 drive_list_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.
drive_list_comments is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.