youtube_delete_video
Delete a YouTube video
This record as markdown: /tools/io-github-alifanov-scopegate/youtube-delete-video.md
What youtube_delete_video does on ScopeGate
AI agents call youtube_delete_video to permanently remove resources in ScopeGate, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why youtube_delete_video is rated Critical
Deleting a YouTube video is a destructive action that cannot be undone. Video metadata, comments, and view history are permanently removed. While it may not affect other users' data directly, it causes permanent loss of the creator's content and constitutes an irreversible operation.
From the tool's definition Tool name explicitly states 'delete_video' and description confirms 'Delete a YouTube video'. This is an irreversible deletion operation.
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 ScopeGate, 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 ScopeGate, apply this rule, and every youtube_delete_video call is checked against it from then on.
Questions about youtube_delete_video
Delete a YouTube video. It is categorised as a Destructive tool in the ScopeGate MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScopeGate 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 ScopeGate. 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 ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue