Add a comment to a Google Doc. Can be anchored to specific text or unanchored. Args: - file_id (string): The ID of the Google Doc - content (string): The text content of the comment - quoted_text (string, optional): Text to anchor the comment to (for anchored comments) Returns: {
AI agents use drive_create_comment to create or update resources in Google Workspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace environment.
This tool creates new comment objects within Google Docs, which is a reversible write operation. Comments can be edited or deleted, making this a Write rather than Destructive action. The blast radius is low since comments are supplementary metadata that do not modify the core document content. No data is irreversibly deleted, no code is executed, and no financial transactions occur.
From the tool's definition Tool name 'drive_create_comment' and description 'Add a comment to a Google Doc' indicates creation of new data (comments). The args show it takes file_id, content, and optional quoted_text to create/add comments.
Documented attack patterns abuse exactly the kind of access drive_create_comment 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_create_comment:
{
"version": "1",
"default": "deny",
"tools": {
"drive_create_comment": {
"limits": [
{
"counter": "drive_create_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}drive_create_comment stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a comment to a Google Doc. Can be anchored to specific text or unanchored. Args: - file_id (string): The ID of the Google Doc - content (string): The text content of the comment - quoted_text (string, optional): Text to anchor the comment to (for anchored comments) Returns: {. It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP server in PolicyLayer and add a rule for drive_create_comment: 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_create_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the drive_create_comment 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_create_comment. 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_create_comment 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.