Delete a video. This action is irreversible.
AI agents call youtube_delete_video to permanently remove resources in YouTube MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a video from YouTube with no undo capability. Deletion is irreversible data destruction, making it Destructive rather than Write. Severity is high because deletion of published content can damage reputation, lose audience engagement metrics, and represent significant content loss, though not directly financial in nature (Financial would apply to monetization controls).
From the tool's definition Tool name 'youtube_delete_video' and description states 'Delete a video. This action is irreversible.'
Attacks that exploit this kind of access
Delete a video. This action is irreversible. It is categorised as a Destructive tool in the YouTube MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the YouTube MCP Server 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 MCP Server. 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 MCP server (pauling-ai/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 →