Critical Risk →

youtube_delete_comment

Permanently delete a YouTube comment by id (or 'youtube:comment:<id>'). Cannot be undone. Costs 50 quota units.

Part of the Dialogbrain server.

youtube_delete_comment can permanently delete data in Dialogbrain, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DIALOGBRAIN →

Free to start. No card required.

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

Without a policy, an AI agent could call youtube_delete_comment in a loop, permanently destroying resources in Dialogbrain. There is no undo for destructive operations. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "youtube_delete_comment"
  ]
}

See the full Dialogbrain policy for all 157 tools.

Get this rule live on your own Dialogbrain server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DIALOGBRAIN →

View all 157 tools →

These attack patterns abuse exactly the kind of access youtube_delete_comment gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so youtube_delete_comment only ever does what you allow.

SECURE DIALOGBRAIN →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the youtube_delete_comment tool do? +

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.

How do I enforce a policy on youtube_delete_comment? +

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.

What risk level is youtube_delete_comment? +

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.

Can I rate-limit youtube_delete_comment? +

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.

How do I block youtube_delete_comment completely? +

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.

What MCP server provides youtube_delete_comment? +

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.

Enforce policy on every Dialogbrain tool call.

Deterministic rules across all 157 Dialogbrain tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.