This record as markdown: /tools/ark7-google-drive-mcp/deletecomment.md
What deleteComment does on Google Drive
AI agents call deleteComment to permanently remove resources in Google Drive, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
commentId | string | Yes | The comment ID to delete |
documentId | string | Yes | The document ID |
Parameters from the server's own tool schema.
Why deleteComment is rated Critical
Deleting comments is a destructive action that cannot be undone without manual recovery. While the blast radius is narrower than deleting entire files or documents (which would be 'critical'), losing comments represents permanent data loss and meets the Destructive threshold. Confidence is high because the action is unambiguous.
From the tool's definition Tool name is 'deleteComment' and description states 'Delete a comment from the document' — the verb 'Delete' clearly indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs deleteComment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteComment, this is the rule to start with:
deleteComment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Drive, apply this rule, and every deleteComment call is checked against it from then on.
Questions about deleteComment
Delete a comment from the document. It is categorised as a Destructive tool in the Google Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
deleteComment accepts 3 parameters: account, commentId, documentId. Required: commentId, documentId. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for deleteComment: 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 Drive. Nothing to install.
deleteComment 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 deleteComment 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 deleteComment. 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.
deleteComment is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
Across the catalogue