Delete a video. Costs 50 quota units. This is irreversible.
AI agents call 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.
Deleting a video is an irreversible action that permanently destroys data and cannot be undone. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The severity is high because unauthorized deletion of videos could damage content creators' work, channel reputation, and audience engagement.
From the tool's definition Tool description explicitly states 'Delete a video' and 'This is irreversible.' The name is 'delete_video' which directly indicates deletion of content.
Attacks that exploit this kind of access
Delete a video. Costs 50 quota units. This is irreversible. 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 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.
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 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 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.
delete_video is provided by the Youtube MCP server (kpfitzgerald/youtube-mcp). 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 →