youtube_delete_comment
Permanently delete a YouTube comment by id (or 'youtube:comment:<id>'). Cannot be undone. Costs 50 quota units.
This record as markdown: /tools/io-github-saloprj-dialogbrain/youtube-delete-comment.md
What youtube_delete_comment does on Dialogbrain
AI agents call youtube_delete_comment to permanently remove resources in Dialogbrain, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
comment_id | string | Yes | Bare commentId OR 'youtube:comment:<id>'. |
Parameters from the server's own tool schema.
Why youtube_delete_comment is rated Critical
This tool irreversibly deletes data (a YouTube comment) with no undo capability. It falls squarely into the Destructive category. Severity is high because, while the blast radius of deleting a single comment is limited in scope, the action cannot be reversed and could affect user content or relationships. The confidence is high (0.95) because the description unambiguously indicates permanent, irreversible deletion.
From the tool's definition Tool description explicitly states 'Permanently delete a YouTube comment' and 'Cannot be undone.' These are the defining characteristics of irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs youtube_delete_comment safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_delete_comment, this is the rule to start with:
youtube_delete_comment 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 Dialogbrain, apply this rule, and every youtube_delete_comment call is checked against it from then on.
Questions about youtube_delete_comment
Permanently delete a YouTube comment by id (or 'youtube:comment:<id>'). Cannot be undone. Costs 50 quota units. It is categorised as a Destructive tool in the Dialogbrain MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
youtube_delete_comment accepts 1 parameter: comment_id. Required: comment_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for youtube_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 Dialogbrain. Nothing to install.
youtube_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 youtube_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 youtube_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.
youtube_delete_comment is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue