youtube_delete_video
Permanently delete a YouTube video by id (or 'youtube:video:<id>'). Cannot be undone. Costs 50 quota units. Caller must own the channel.
This record as markdown: /tools/io-github-saloprj-dialogbrain/youtube-delete-video.md
What youtube_delete_video does on Dialogbrain
AI agents call youtube_delete_video 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 |
|---|---|---|---|
video_id | string | Yes | Bare videoId OR 'youtube:video:<id>'. |
Parameters from the server's own tool schema.
Why youtube_delete_video is rated Critical
This tool irreversibly deletes data (a YouTube video) with no possibility of recovery. While the blast radius is somewhat limited by the requirement that the caller must own the channel, the permanent and irreversible nature of the action makes it Destructive rather than Write. Destructive is the correct category per the hierarchy when an action cannot be undone.
From the tool's definition Tool description explicitly states "Permanently delete a YouTube video" and "Cannot be undone." The name contains "delete" and the description uses "Permanently" and "Cannot be undone" which are hallmarks of destructive operations.
Attacks that exploit this kind of access
The rule that runs youtube_delete_video 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_video, this is the rule to start with:
youtube_delete_video 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_video call is checked against it from then on.
Questions about youtube_delete_video
Permanently delete a YouTube video by id (or 'youtube:video:<id>'). Cannot be undone. Costs 50 quota units. Caller must own the channel. 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_video accepts 1 parameter: video_id. Required: video_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_video: 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_video 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_video 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_video. 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_video 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