Get detailed analytics for a specific video over time.
AI agents call youtube_analytics_video_detail 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 and queries analytics data for a video without creating, modifying, deleting, executing commands, or initiating financial transactions. It falls squarely into the Read category as a data retrieval operation. Severity is low because misuse would only expose channel analytics information, not cause operational harm, data loss, or financial impact.
From the tool's definition Tool name 'youtube_analytics_video_detail' and description 'Get detailed analytics for a specific video over time' indicate data retrieval without modification. The verb 'Get' and context of analytics reporting confirm read-only access to existing data.
Attacks that exploit this kind of access
Get detailed analytics for a specific video over time. 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_video_detail: 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_video_detail 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_video_detail 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_video_detail. 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_video_detail 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 →