GOOGLESUPER_DELETE_REPLY
Tool to delete a specific reply by reply ID. Use when you need to remove a reply from a comment on a file.
This record as markdown: /tools/googlesuper/googlesuper-delete-reply.md
What GOOGLESUPER_DELETE_REPLY does on Google Super
AI agents call GOOGLESUPER_DELETE_REPLY to permanently remove resources in Google Super, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_id | string | — | The ID of the file. |
reply_id | string | — | The ID of the reply. |
comment_id | string | — | The ID of the comment. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_DELETE_REPLY is rated Critical
Deleting a reply is an irreversible action that destroys data without the ability to undo it. This fits the Destructive category definition. While the blast radius is narrower than a bulk delete (affecting a single reply rather than an entire dataset), accidental or malicious deletion of replies in collaborative environments (Google Drive comments, Gmail threads, etc.) could cause loss of important communication or…
From the tool's definition Tool name contains 'DELETE' and description states 'delete a specific reply' — this is an irreversible operation that removes data.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_DELETE_REPLY safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_DELETE_REPLY, this is the rule to start with:
GOOGLESUPER_DELETE_REPLY 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 Super, apply this rule, and every GOOGLESUPER_DELETE_REPLY call is checked against it from then on.
Questions about GOOGLESUPER_DELETE_REPLY
Tool to delete a specific reply by reply ID. Use when you need to remove a reply from a comment on a file. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
GOOGLESUPER_DELETE_REPLY accepts 3 parameters: file_id, reply_id, comment_id. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_DELETE_REPLY: 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 Super. Nothing to install.
GOOGLESUPER_DELETE_REPLY 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 GOOGLESUPER_DELETE_REPLY 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 GOOGLESUPER_DELETE_REPLY. 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.
GOOGLESUPER_DELETE_REPLY is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
Across the catalogue