Get video metadata by URL or ID.
AI agents call youtube_video_info to retrieve information from Youtube Research without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval only. It fetches and returns metadata about YouTube videos without modifying, deleting, or executing anything. The blast radius of misuse is minimal — an attacker could enumerate video information or gather intelligence, but cannot modify content, trigger actions, or cause financial harm. This is a standard Read classification.
From the tool's definition Tool retrieves video metadata by URL or ID — a query operation with no side effects. Description uses 'Get' which is a read operation.
Attacks that exploit this kind of access
Get video metadata by URL or ID. It is categorised as a Read tool in the Youtube Research MCP Server, which means it retrieves data without modifying state.
Register the Youtube Research MCP server in PolicyLayer and add a rule for youtube_video_info: 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 Research. Nothing to install.
youtube_video_info 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_info 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_info. 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_info is provided by the Youtube Research MCP server (plaguedoctor39/youtube-research). 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 →