AI agents call getTrendingVideos to retrieve information from Yt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns publicly available trending video information without modifying, deleting, or executing any operations. It has no side effects and presents minimal risk—the worst outcome is returning incorrect trending data, which cannot harm systems or data integrity.
From the tool's definition Tool description states 'Retrieves trending videos' and 'Returns a list of videos'; uses passive retrieval language. Context includes sibling tools (getChannelPlaylists, getPlaylistDetails, getTranscripts) that are all read-only queries against YouTube data.
Attacks that exploit this kind of access
Retrieves trending videos based on region and category. Returns a list of videos that are currently popular in the specified region and category. Use this when you want to discover what. It is categorised as a Read tool in the Yt MCP Server, which means it retrieves data without modifying state.
Register the Yt MCP server in PolicyLayer and add a rule for getTrendingVideos: 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 Yt. Nothing to install.
getTrendingVideos 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 getTrendingVideos 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 getTrendingVideos. 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.
getTrendingVideos is provided by the Yt MCP server (yt-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 →