发现 YouTube Shorts 上的潜在热门视频。
AI agents call get_youtube_shorts_trends to retrieve information from Viral Shorts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool discovers and retrieves trending video information using the YouTube Data API. It queries existing public data about YouTube Shorts trends without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could at most retrieve unwanted trend data or make excessive API calls, but no data is at risk of being altered or lost.
From the tool's definition Tool name and context indicate data discovery and querying of trending videos from YouTube Shorts. Description translates to 'Discover potential viral videos on YouTube Shorts' — a retrieval operation.
Attacks that exploit this kind of access
发现 YouTube Shorts 上的潜在热门视频。. It is categorised as a Read tool in the Viral Shorts MCP Server, which means it retrieves data without modifying state.
Register the Viral Shorts MCP server in PolicyLayer and add a rule for get_youtube_shorts_trends: 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 Viral Shorts. Nothing to install.
get_youtube_shorts_trends 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_youtube_shorts_trends 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_youtube_shorts_trends. 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_youtube_shorts_trends is provided by the Viral Shorts MCP server (xeron2000/viral-shorts). 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 →