AI agents call trending_analysis to retrieve information from Yt Fetch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and analyzes publicly available YouTube trending data. It retrieves information but does not create, modify, delete, execute code, or commit financial transactions. The analysis is performed on fetched data without altering any state. This is a straightforward Read category tool with low blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Get and analyze trending videos in specific categories' - retrieves and analyzes publicly available trending data without modification.
Attacks that exploit this kind of access
Get and analyze trending videos in specific categories. It is categorised as a Read tool in the Yt Fetch MCP Server, which means it retrieves data without modifying state.
Register the Yt Fetch MCP server in PolicyLayer and add a rule for trending_analysis: 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 Fetch. Nothing to install.
trending_analysis 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 trending_analysis 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 trending_analysis. 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.
trending_analysis is provided by the Yt Fetch MCP server (smith-nathanh/yt-fetch). 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 →