Get trending videos for a region.
AI agents call get_trending_videos_tool to retrieve information from YouTube MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available trending video metadata from YouTube for a specified region. It has no side effects, does not modify or delete data, does not execute code or external operations, and involves no financial transactions. It is a straightforward read operation that retrieves information from a public API.
From the tool's definition Tool name contains 'get' and description states 'Get trending videos for a region' — a retrieval operation with no data modification, deletion, code execution, or financial implications.
Attacks that exploit this kind of access
Get trending videos for a region. It is categorised as a Read tool in the YouTube MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YouTube MCP Server MCP server in PolicyLayer and add a rule for get_trending_videos_tool: 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. Nothing to install.
get_trending_videos_tool 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_tool 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_tool. 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_tool is provided by the YouTube MCP Server MCP server (temiedani/youtube-mcp-server). 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 →