drive_delete_comment

THE RISK

Critical Risk

Why drive_delete_comment needs a policy

This tool permanently removes a comment, which cannot be undone. Although the scope is limited to a single comment (not the entire document), deletion is inherently destructive. The high severity reflects that an agent could maliciously purge all comments from a document to erase feedback, discussions, or audit trails. Confidence is high because the intent is explicit in both name and description.

From the tool's definition Tool name contains 'delete' and description states 'Delete a comment from a Google Doc' — irreversible removal of data.

Documented attack patterns abuse exactly the kind of access drive_delete_comment gives an agent:

POLICY

How to control drive_delete_comment

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_delete_comment:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "drive_delete_comment"
  ]
}

drive_delete_comment disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Google Workspace — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Google Workspace tools

Destructive sheets_clear_values Clear cell values from a specific range in a Google Spreadsheet (keeps formatting). Args: Write docs_batch_update Apply batch updates to a Google Doc (insert/update/delete text, formatting, images, tables Write docs_create_document Create a new Google Doc with an optional initial body. Args: - title (string): The titl Write sheets_append_values Append rows of data to the end of a table in a Google Spreadsheet. Args: - spreadsheet_ Write sheets_duplicate_sheet Duplicate a sheet within the same spreadsheet. Args: - spreadsheet_id (string): The ID Write drive_copy_file Create a copy of a file in Google Drive. Args: - file_id (string): The ID of the file t Write drive_create_comment Add a comment to a Google Doc. Can be anchored to specific text or unanchored. Args: - Write drive_reply_to_comment Reply to an existing comment on a Google Doc. Args: - file_id (string): The ID of the G

All 34 Google Workspace tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Google Workspace → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about drive_delete_comment

What does the drive_delete_comment tool do? +

Delete a comment from a Google Doc. Args: - file_id (string): The ID of the Google Doc - comment_id (string): The ID of the comment to delete Returns: {. It is categorised as a Destructive tool in the Google Workspace MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on drive_delete_comment? +

Register the Google Workspace MCP server in PolicyLayer and add a rule for drive_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 Workspace. Nothing to install.

What risk level is drive_delete_comment? +

drive_delete_comment is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit drive_delete_comment? +

Yes. Add a rate_limit block to the drive_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.

How do I block drive_delete_comment completely? +

Set action: deny in the PolicyLayer policy for drive_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.

What MCP server provides drive_delete_comment? +

drive_delete_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.

Enforce policy on every Google Workspace tool call.

Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →