Upload a local video file to YouTube. Calls videos.insert with a resumable media upload. The file is streamed from disk via fs.createReadStream so large files are handled without loading them fully into memory. Note: This operation costs approximately 1600 quota units. Args - filePath (string, re...
AI agents use youtube_upload_video to create or update resources in Youtube — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Youtube environment.
This tool creates new data (video uploads) on a public YouTube channel, which is reversible (videos can be deleted via youtube_delete_video). While it modifies the channel state and could have significant business/reputational impact if misused by an AI agent (uploading inappropriate content), it is fundamentally a Write operation rather than Destructive or Execute.
From the tool's definition Tool description states 'Upload a local video file to YouTube' and 'Calls videos.insert with a resumable media upload.' This creates new content on the YouTube channel.
Attacks that exploit this kind of access
Upload a local video file to YouTube. Calls videos.insert with a resumable media upload. The file is streamed from disk via fs.createReadStream so large files are handled without loading them fully into memory. Note: This operation costs approximately 1600 quota units. Args - filePath (string, required): absolute path to the local video file - title (string, required): video title (shown on YouTube) - description (string, optional): video description - tags (string[], optional): tags / keywords - categoryId (string, optional): numeric category ID, default. It is categorised as a Write tool in the Youtube MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Youtube 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 Youtube. 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 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 →