youtube_update_video
Update metadata for a YouTube video
This record as markdown: /tools/io-github-alifanov-scopegate/youtube-update-video.md
What youtube_update_video does on ScopeGate
AI agents use youtube_update_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_update_video is rated Medium
The tool modifies video metadata (title, description, tags, privacy settings, etc.) but does not delete or destroy the video or its content. Metadata updates are reversible—they can be changed again.
From the tool's definition Tool name contains 'update' and description states 'Update metadata for a YouTube video', indicating reversible modification of existing data.
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 ScopeGate, 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 ScopeGate, apply this rule, and every youtube_update_video call is checked against it from then on.
Questions about youtube_update_video
Update metadata for a YouTube video. 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_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 ScopeGate. 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 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