Get deep details for a specific YouTube video: full stats, tags, description, thumbnail, and engagement rate.
AI agents call get_video_details to retrieve information from YouTube MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata and analytics for a YouTube video. It performs no side effects, creates no data, executes no code, and modifies nothing. The action is purely informational retrieval, fitting the Read category. Severity is low because exposure of this tool poses minimal risk—viewing one's own video details is a standard, safe operation with no blast radius for misuse.
From the tool's definition Tool description states it 'Get[s] deep details for a specific YouTube video: full stats, tags, description, thumbnail, and engagement rate.' The verb 'get' and list of retrieved data (stats, tags, description, thumbnail, engagement rate) indicate read-only…
Attacks that exploit this kind of access
Get deep details for a specific YouTube video: full stats, tags, description, thumbnail, and engagement rate. It is categorised as a Read tool in the YouTube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server MCP server in PolicyLayer and add a rule for get_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 YouTube MCP Server. Nothing to install.
get_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 get_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 get_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.
get_video_details is provided by the YouTube MCP Server MCP server (sulavkharel/youtube-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →