Delete a comment from a document.
AI agents call delete_comment to permanently remove resources in Google Docs MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While deleting a comment may seem less severe than deleting an entire document, it is still an irreversible operation that removes data that cannot be recovered through normal means. This falls squarely into the Destructive category because the action cannot be undone by the user without manual recovery or backups.
From the tool's definition Tool name is 'delete_comment' and description states 'Delete a comment from a document.' The verb 'delete' combined with the irreversible nature of removing a comment from a Google Doc indicates destructive capability.
Attacks that exploit this kind of access
Delete a comment from a document. It is categorised as a Destructive tool in the Google Docs MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for delete_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 Docs MCP Server. Nothing to install.
delete_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_comment is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). 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 →