youtube.video_details
Fetch metadata for a public YouTube video by video id or URL. Accepts a bare 11-character video id (for example PuQFESk0BrA) or common YouTube watch, youtu.be, Shorts, and embed URLs. Returns title, description, view count, duration, publish date, channel id, category, keywords, and thumbnails. C...
This record as markdown: /tools/io-github-vee3io-vee3/youtube.video-details.md
What youtube.video_details does on Vee3
AI agents call youtube.video_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 |
|---|---|---|---|
video_id | string | Yes | YouTube video id or URL (for example PuQFESk0BrA, https://youtu.be/PuQFESk0BrA, or https://www.youtube.com/watch?v=PuQFESk0BrA). |
Parameters from the server's own tool schema.
Why youtube.video_details is rated Low
This tool retrieves publicly available metadata from YouTube videos with no side effects. It does not create, modify, delete, or execute any operations. The data returned (title, description, view count, etc.) is already public and the tool only queries it.
From the tool's definition Tool description explicitly states 'Fetch metadata' and 'Returns title, description, view count, duration, publish date, channel id, category, keywords, and thumbnails' — all read-only operations on public data with no modification capability.
Attacks that exploit this kind of access
The rule that runs youtube.video_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.video_details, this is the rule to start with:
youtube.video_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.video_details call is checked against it from then on.
Questions about youtube.video_details
Fetch metadata for a public YouTube video by video id or URL. Accepts a bare 11-character video id (for example PuQFESk0BrA) or common YouTube watch, youtu.be, Shorts, and embed URLs. Returns title, description, view count, duration, publish date, channel id, category, keywords, and thumbnails. Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
youtube.video_details accepts 1 parameter: video_id. Required: video_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.video_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.video_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.video_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.video_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.video_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