youtube_upload_video
AI agents use youtube_upload_video to create or update resources in YouTube MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your YouTube MCP Server environment.
Uploading a video creates new content on a YouTube channel—a reversible Write operation. Not Execute (doesn't run arbitrary code), not Destructive (upload is not irreversible; videos can be deleted), not Financial. Severity is high because an AI agent misusing this could spam, publish inappropriate content to a large audience, or damage a channel's reputation.
From the tool's definition Tool name 'youtube_upload_video' indicates video publishing capability. Server description explicitly lists 'video publishing' as a core function. No description provided for this specific tool.
Attacks that exploit this kind of access
youtube_upload_video. It is categorised as a Write tool in the YouTube MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the YouTube MCP Server 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 MCP Server. 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 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 →