youtube.channel_videos
Fetch a paginated list of videos from a public YouTube channel by its channel id. Accepts a channel id (for example UCg6gPGh8HU2U01vaFCAsvmQ) or common YouTube channel URLs (for example https://www.youtube.com/@ChrisTitusTech). Use cursor from a prior response for the next page. Cost = 10 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/youtube.channel-videos.md
What youtube.channel_videos does on Vee3
AI agents call youtube.channel_videos to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
cursor | object | — | Pagination cursor from a previous response cursor field. |
channel_id | string | Yes | YouTube channel id or URL (for example UCg6gPGh8HU2U01vaFCAsvmQ or https://www.youtube.com/@ChrisTitusTech). |
Parameters from the server's own tool schema.
Why youtube.channel_videos is rated Low
This tool retrieves and queries publicly available YouTube channel video data. It has no capability to modify, delete, execute code, transfer funds, or perform any operations with side effects. The operation is read-only and operates on public information accessible via normal YouTube browsing.
From the tool's definition Tool description states "Fetch a paginated list of videos from a public YouTube channel" - this is a retrieval operation with no side effects. It queries public data and returns video listings.
Attacks that exploit this kind of access
The rule that runs youtube.channel_videos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For youtube.channel_videos, this is the rule to start with:
youtube.channel_videos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every youtube.channel_videos call is checked against it from then on.
Questions about youtube.channel_videos
Fetch a paginated list of videos from a public YouTube channel by its channel id. Accepts a channel id (for example UCg6gPGh8HU2U01vaFCAsvmQ) or common YouTube channel URLs (for example https://www.youtube.com/@ChrisTitusTech). Use cursor from a prior response for the next page. Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
youtube.channel_videos accepts 2 parameters: cursor, channel_id. Required: channel_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for youtube.channel_videos: 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 Vee3. Nothing to install.
youtube.channel_videos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the youtube.channel_videos 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.channel_videos. 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.channel_videos is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue