youtube_analytics_revenue_by_video
AI agents call youtube_analytics_revenue_by_video 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 appears to query YouTube Analytics API to retrieve revenue data segmented by individual videos. It has no side effects—it retrieves historical or current financial reporting data without creating, modifying, or deleting anything.
From the tool's definition Tool name 'youtube_analytics_revenue_by_video' indicates retrieval of analytics data (revenue metrics broken down by video). No description provided, but naming pattern matches sibling tools (youtube_analytics_*) which are query/retrieval operations.
Attacks that exploit this kind of access
youtube_analytics_revenue_by_video. 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_revenue_by_video: 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_revenue_by_video 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_revenue_by_video 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_revenue_by_video. 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_revenue_by_video 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 →