youtube.channel_details
Fetch metadata for a public YouTube channel by channel id or URL. Accepts a channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg) or common YouTube channel URLs (for example https://www.youtube.com/@WWE). Returns title, username, description, subscriber and view counts, join date, verification flags,...
This record as markdown: /tools/io-github-vee3io-vee3/youtube.channel-details.md
What youtube.channel_details does on Vee3
AI agents call youtube.channel_details 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 |
|---|---|---|---|
channel_id | string | Yes | YouTube channel id or URL (for example UCJ5v_MCY6GNUBTO8-D3XoAg or https://www.youtube.com/@WWE). |
Parameters from the server's own tool schema.
Why youtube.channel_details is rated Low
This tool retrieves publicly available information about YouTube channels. It performs a query operation with no side effects—no data is created, modified, deleted, or altered. The information returned (channel metadata, counts, images, links) is read-only access to public information.
From the tool's definition Tool description uses 'Fetch metadata' and 'Returns title, username, description, subscriber and view counts, join date, verification flags, avatar and banner images, keywords, and external links.' These are all retrieval operations on public YouTube channel…
Attacks that exploit this kind of access
The rule that runs youtube.channel_details 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_details, this is the rule to start with:
youtube.channel_details 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_details call is checked against it from then on.
Questions about youtube.channel_details
Fetch metadata for a public YouTube channel by channel id or URL. Accepts a channel id (for example UCJ5v_MCY6GNUBTO8-D3XoAg) or common YouTube channel URLs (for example https://www.youtube.com/@WWE). Returns title, username, description, subscriber and view counts, join date, verification flags, avatar and banner images, keywords, and external links. 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_details accepts 1 parameter: 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_details: 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_details 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_details 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_details. 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_details 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