Get detailed metadata and statistics for a specific video.
AI agents call youtube_get_video 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 retrieves and queries video metadata and statistics without creating, modifying, deleting, or executing any operations. It is a passive read operation analogous to fetching or getting data. The severity is low because retrieving publicly available or channel-owned video metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool is described as 'Get detailed metadata and statistics for a specific video' — a retrieval operation with no modification or execution implied.
Attacks that exploit this kind of access
Get detailed metadata and statistics for a specific video. 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 youtube_get_video: 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.
youtube_get_video 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_get_video 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_get_video. 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_get_video is provided by the YouTube MCP Server MCP server (pauling-ai/youtube-mcp-server). 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 →