youtube.channel_search
Search public videos on a YouTube channel by keyword or phrase. Accepts a bare channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg), not a URL. Returns matching video entries and cursorNext for pagination. Use cursorNext from a prior response as cursor for the next page. Cost = 10 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/youtube.channel-search.md
What youtube.channel_search does on Vee3
AI agents call youtube.channel_search 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 |
|---|---|---|---|
query | string | Yes | Search keywords or phrase within the channel. |
cursor | object | — | Pagination cursor from cursorNext. |
channel_id | string | Yes | YouTube channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg, not a URL). |
Parameters from the server's own tool schema.
Why youtube.channel_search is rated Low
This tool queries publicly available YouTube data and returns results. It performs no writes, deletions, code execution, or financial operations. The search functionality is a standard read operation with no blast radius—the worst case is returning incorrect or irrelevant search results to an agent, which has minimal security impact.
From the tool's definition Tool description explicitly states 'Search public videos on a YouTube channel' and 'Returns matching video entries and cursorNext for pagination.' The verbs are 'search' and 'returns'—both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs youtube.channel_search 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_search, this is the rule to start with:
youtube.channel_search 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_search call is checked against it from then on.
Questions about youtube.channel_search
Search public videos on a YouTube channel by keyword or phrase. Accepts a bare channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg), not a URL. Returns matching video entries and cursorNext for pagination. Use cursorNext from a prior response as cursor 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_search accepts 3 parameters: query, cursor, channel_id. Required: query, 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_search: 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_search 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_search 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_search. 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_search 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