Update the metadata of an existing video. Fetches the current video (snippet + status) first, merges your provided fields, then calls videos.update. This ensures snippet.title and snippet.categoryId (both required by the API) are always present even if you only change one field. Args - videoId (s...
AI agents use youtube_update_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 modifies existing video data (title, description, tags, category, privacy status) but does not delete or destroy content, nor does it execute arbitrary code or move money. It is a Write operation because it creates or modifies data reversibly.
From the tool's definition Tool description states it 'Update[s] the metadata of an existing video' and 'calls videos.update' with optional parameters like title, description, tags, categoryId, and privacyStatus. These are reversible modifications to video metadata.
Attacks that exploit this kind of access
Update the metadata of an existing video. Fetches the current video (snippet + status) first, merges your provided fields, then calls videos.update. This ensures snippet.title and snippet.categoryId (both required by the API) are always present even if you only change one field. Args - videoId (string, required): video to update - title (string, optional): new title - description (string, optional): new description - tags (string[], optional): full replacement tag list - categoryId (string, optional): numeric category ID (use youtube_list_video_categories) - privacyStatus (. 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_update_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_update_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_update_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_update_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_update_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 →