get_trending_videos
AI agents call get_trending_videos to retrieve information from YouTube MCP Server Enhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trending video information from YouTube without modifying, executing, or deleting data. It has no side effects beyond querying public data. Confidence is high based on the consistent read-only pattern of sibling tools and the retrieval nature of the name, despite the empty description.
From the tool's definition Tool name 'get_trending_videos' and server context indicate data retrieval of YouTube trending video metadata. No description provided, but sibling tools (get_channel_info, get_video_info, get_playlist_info) are all read-only data extraction operations.
Attacks that exploit this kind of access
get_trending_videos. It is categorised as a Read tool in the YouTube MCP Server Enhanced MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server Enhanced MCP server in PolicyLayer and add a rule for get_trending_videos: 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 Enhanced. Nothing to install.
get_trending_videos 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_trending_videos 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_trending_videos. 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_trending_videos is provided by the YouTube MCP Server Enhanced MCP server (labeveryday/youtube-mcp-server-enhanced). 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 →