Marks a comment as resolved. NOTE: Due to Google API limitations, the Drive API does not support resolving comments on Google Docs files. This operation will attempt to update the comment but the resolved status may not persist in the UI. Comments can be resolved manually in the Google Docs inter...
AI agents use resolveComment to create or update resources in Google Workspace MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace MCP Server environment.
This tool creates or modifies data reversibly by changing comment metadata (resolved status). It falls under Write rather than Read (retrieves data) or Execute (runs arbitrary code).
From the tool's definition Marks a comment as resolved - this modifies the state of a comment object, changing its resolved status from unresolved to resolved. The description explicitly states this is an update operation, though with limitations on persistence.
Documented attack patterns abuse exactly the kind of access resolveComment 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 resolveComment:
{
"version": "1",
"default": "deny",
"tools": {
"resolveComment": {
"limits": [
{
"counter": "resolvecomment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resolveComment 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.
Marks a comment as resolved. NOTE: Due to Google API limitations, the Drive API does not support resolving comments on Google Docs files. This operation will attempt to update the comment but the resolved status may not persist in the UI. Comments can be resolved manually in the Google Docs interface. It is categorised as a Write tool in the Google Workspace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for resolveComment: 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.
resolveComment 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 resolveComment 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 resolveComment. 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.
resolveComment 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.