Gets a specific comment with its full thread of replies.
AI agents call getComment to retrieve information from Google Docs & Drive 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 reads comment data from Google Docs. It performs no mutations, deletions, or external operations—only fetches information. The blast radius of misuse is minimal: an attacker could read comments they may not have access to, but cannot modify, delete, or execute actions. This is clearly a Read operation.
From the tool's definition Tool name 'getComment' and description 'Gets a specific comment with its full thread of replies' indicate a retrieval operation that queries existing comment data without modification or side effects.
Attacks that exploit this kind of access
Gets a specific comment with its full thread of replies. It is categorised as a Read tool in the Google Docs & Drive MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Docs & Drive MCP Server MCP server in PolicyLayer and add a rule for getComment: 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 Docs & Drive MCP Server. Nothing to install.
getComment 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 getComment 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 getComment. 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.
getComment is provided by the Google Docs & Drive MCP Server MCP server (oregpt/agenticledger_mcp_docsonly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →