youtube_run_analytics_query · Youtube MCP: Risk & Policy

WHAT IT DOES

What youtube_run_analytics_query does on Youtube

AI agents invoke youtube_run_analytics_query to trigger actions in Youtube. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why youtube_run_analytics_query needs a policy

This is an Execute tool because it runs queries with arguments that determine outcome. While reads are typically lower-risk, the ability to execute arbitrary analytics API queries with flexible parameters—combined with the server's elevated privileges over a full YouTube channel (as noted in server description)—creates risk if an AI agent constructs malicious or unintended queries.

From the tool's definition Tool executes arbitrary 'flexible YouTube Analytics API query' with user-provided 'metrics, dimensions, filters, and sort orders' against the authenticated channel.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

youtube_run_analytics_query Rate-limited

youtube_run_analytics_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "youtube_run_analytics_query": {
      "limits": [
        {
          "counter": "youtube_run_analytics_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Youtube, so you can run agents against it safely.

FAQ

Questions about youtube_run_analytics_query

What does the youtube_run_analytics_query tool do? +

Execute a flexible YouTube Analytics API query against the authenticated channel. Supports any combination of metrics, dimensions, filters, and sort orders supported by the YouTube Analytics API v2. startDate and endDate default to the last 28 days when omitted. Args: - \. It is categorised as a Execute tool in the Youtube MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on youtube_run_analytics_query? +

Register the Youtube MCP server in PolicyLayer and add a rule for youtube_run_analytics_query: 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.

What risk level is youtube_run_analytics_query? +

youtube_run_analytics_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit youtube_run_analytics_query? +

Yes. Add a rate_limit block to the youtube_run_analytics_query 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.

How do I block youtube_run_analytics_query completely? +

Set action: deny in the PolicyLayer policy for youtube_run_analytics_query. 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.

What MCP server provides youtube_run_analytics_query? +

youtube_run_analytics_query 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.