Lists all comments in a Google Document.
AI agents call listComments to retrieve information from Google Workspace MCP Server 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 comment data from a Google Document without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal risk—an AI agent querying comments cannot cause unintended harm. Severity is low because comment metadata is typically less sensitive than document content, and listing does not expose write or destructive capabilities.
From the tool's definition Tool name is 'listComments' and description states it 'Lists all comments in a Google Document.' The verb 'Lists' indicates a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access listComments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for listComments:
{
"version": "1",
"default": "deny",
"tools": {
"listComments": {}
}
}listComments 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.
Lists all comments in a Google Document. It is categorised as a Read tool in the Google Workspace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP Server 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 Workspace MCP Server. 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 Workspace MCP Server MCP server (sputnicyoji/google-workspace-mcp-with-script). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace MCP Server, 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.
72 Google Workspace MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.