youtube_update_video
Update title, description, privacy, or tags on a YouTube video. Costs 1600 quota units. Only fields provided are changed.
This record as markdown: /tools/io-github-saloprj-dialogbrain/youtube-update-video.md
What youtube_update_video does on Dialogbrain
AI agents use youtube_update_video to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tags | array | — | New tags list. Omit to keep current. |
title | string | — | New title (max 100 chars). Omit to keep current. |
privacy | string | — | 'private', 'unlisted', or 'public'. Omit to keep current. |
video_id | string | Yes | Bare videoId OR 'youtube:video:<id>'. |
description | string | — | New description (max 5000 chars). Omit to keep current. |
Parameters from the server's own tool schema.
Why youtube_update_video is rated Medium
This tool modifies metadata on existing YouTube videos reversibly. Updates to titles, descriptions, privacy settings, and tags can all be undone or corrected later. While this could impact content visibility or audience perception (hence medium severity rather than low), it does not delete data, execute arbitrary code, or involve financial transactions.
From the tool's definition The tool description explicitly states it can "Update title, description, privacy, or tags on a YouTube video." The verb 'update' and the specification of modifiable fields (title, description, privacy, tags) indicate data modification capability.
Attacks that exploit this kind of access
The rule that runs youtube_update_video safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube_update_video, this is the rule to start with:
youtube_update_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 Dialogbrain, apply this rule, and every youtube_update_video call is checked against it from then on.
Questions about youtube_update_video
Update title, description, privacy, or tags on a YouTube video. Costs 1600 quota units. Only fields provided are changed. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
youtube_update_video accepts 5 parameters: tags, title, privacy, video_id, description. Required: video_id. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain 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 Dialogbrain. 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 Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue