youtube_analytics_traffic_sources
AI agents call youtube_analytics_traffic_sources 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 retrieves YouTube analytics data about traffic sources to a channel. Analytics queries are non-destructive read operations that query existing data without side effects. The empty description lowers confidence slightly, but the naming convention and context from sibling analytics tools strongly indicate this is a read-only analytics endpoint.
From the tool's definition Tool name 'youtube_analytics_traffic_sources' follows the 'youtube_analytics_*' pattern consistently used across sibling tools which are all read-only analytics queries (daily, demographics, geography, retention, revenue, etc.).
Attacks that exploit this kind of access
youtube_analytics_traffic_sources. 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 youtube_analytics_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 MCP Server. Nothing to install.
youtube_analytics_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_analytics_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_analytics_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_analytics_traffic_sources is provided by the YouTube MCP Server MCP server (pauling-ai/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 →