Critical Risk →

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.

Single-target operation

Part of the Google Super MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

googlesuper Destructive

AI agents may call GOOGLESUPER_DELETE_REPLY to permanently remove or destroy resources in Google Super. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call GOOGLESUPER_DELETE_REPLY in a loop, permanently destroying resources in Google Super. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

googlesuper.yaml
tools:
  GOOGLESUPER_DELETE_REPLY:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Google Super policy for all 200 tools.

Tool Name GOOGLESUPER_DELETE_REPLY
Category Destructive
Risk Level Critical

View all 200 tools →

Agents calling destructive-class tools like GOOGLESUPER_DELETE_REPLY have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

GOOGLESUPER_DELETE_REPLY is one of the critical-risk operations in Google Super. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the GOOGLESUPER_DELETE_REPLY tool do? +

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.

How do I enforce a policy on GOOGLESUPER_DELETE_REPLY? +

Add a rule in your Intercept YAML policy under the tools section for GOOGLESUPER_DELETE_REPLY. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Super MCP server.

What risk level is GOOGLESUPER_DELETE_REPLY? +

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.

Can I rate-limit GOOGLESUPER_DELETE_REPLY? +

Yes. Add a rate_limit block to the GOOGLESUPER_DELETE_REPLY rule in your Intercept 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 GOOGLESUPER_DELETE_REPLY completely? +

Set action: deny in the Intercept 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.

What MCP server provides GOOGLESUPER_DELETE_REPLY? +

GOOGLESUPER_DELETE_REPLY is provided by the Google Super MCP server (googlesuper). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.