youtube_upload_video
Upload a video to YouTube from a URL. Downloads the video from the provided URL and uploads it via the YouTube resumable upload API. Returns the created video resource including video ID.
This record as markdown: /tools/io-github-alifanov-scopegate/youtube-upload-video.md
What youtube_upload_video does on ScopeGate
AI agents use youtube_upload_video to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why youtube_upload_video is rated Medium
This tool creates new, persistent content on YouTube. While not destructive (can be manually deleted later) or financial, uploading video to a public platform is a significant write operation with potential reputational and copyright implications if misused by an agent. High severity due to the public-facing nature and difficulty of fully removing published content from search/cache.
From the tool's definition Tool description states 'Upload a video to YouTube' and 'uploads it via the YouTube resumable upload API. Returns the created video resource' — this creates new content on a public platform.
Attacks that exploit this kind of access
The rule that runs youtube_upload_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_upload_video, this is the rule to start with:
youtube_upload_video stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every youtube_upload_video call is checked against it from then on.
Questions about youtube_upload_video
Upload a video to YouTube from a URL. Downloads the video from the provided URL and uploads it via the YouTube resumable upload API. Returns the created video resource including video ID. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for youtube_upload_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_upload_video is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the youtube_upload_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_upload_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_upload_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.
This server
Across the catalogue