AI agents call youtube_traffic_sources to retrieve information from Youtube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytics information about traffic sources to a YouTube channel. It is a read-only operation that queries existing data (viewer traffic metrics) with no side effects, no data modification, no code execution, and no destructive actions. The low severity reflects that misuse would only expose analytics data already accessible to the channel owner.
From the tool's definition Tool name 'youtube_traffic_sources' and description 'Show how viewers find the channel' indicate a query/retrieval operation that displays analytics data without modifying or deleting any content.
Attacks that exploit this kind of access
Show how viewers find the channel. It is categorised as a Read tool in the Youtube MCP Server, which means it retrieves data without modifying state.
Register the Youtube MCP server in PolicyLayer and add a rule for youtube_traffic_sources: 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. Nothing to install.
youtube_traffic_sources 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 youtube_traffic_sources 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 youtube_traffic_sources. 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.
youtube_traffic_sources is provided by the Youtube MCP server (tuitamogamer-gpt/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 →