Permanently delete a video from the authenticated channel. This action is irreversible. You must pass confirm:true to proceed. Args - videoId (string, required): ID of the video to delete - confirm (boolean, required): must be true to proceed — safety guard Returns Short confirmation that the vid...
AI agents call youtube_delete_video to permanently remove resources in Youtube — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a YouTube video) from the authenticated channel, which cannot be undone. Deletion tools are classified as Destructive per the category hierarchy. The critical severity reflects the high blast radius—an AI agent misusing this tool could permanently erase valuable video content, channel history, and associated engagement metrics without recovery options.
From the tool's definition Tool description states 'Permanently delete a video from the authenticated channel' and 'This action is irreversible.' The tool name 'youtube_delete_video' explicitly indicates deletion. The description confirms the irreversible nature of the operation.
Attacks that exploit this kind of access
Permanently delete a video from the authenticated channel. This action is irreversible. You must pass confirm:true to proceed. Args - videoId (string, required): ID of the video to delete - confirm (boolean, required): must be true to proceed — safety guard Returns Short confirmation that the video was deleted. Examples - Delete: \. It is categorised as a Destructive tool in the Youtube MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Youtube 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 Youtube. 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 Youtube MCP server (tuitamogamer-gpt/youtube-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →