Get trending/most popular videos for a region.
AI agents call youtube_trending 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 queries YouTube's trending video data and returns metadata results. It has no side effects, creates no data, executes no scripts, and deletes nothing. It is purely informational retrieval, matching the Read category definition.
From the tool's definition Tool returns trending/most popular videos for a region—a retrieval operation with no modification, deletion, or execution of external commands. Description uses 'Get', indicating data fetch only.
Attacks that exploit this kind of access
Get trending/most popular videos for a region. 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_trending: 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_trending 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_trending 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_trending. 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_trending 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 →