ga4_run_report_raw · SEO Analytics MCP: Risk & Policy

WHAT IT DOES

What ga4_run_report_raw does on SEO Analytics MCP

AI agents invoke ga4_run_report_raw to trigger actions in SEO Analytics MCP. 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 ga4_run_report_raw needs a policy

This tool executes a configurable query against the GA4 reporting API with user-supplied filters and ordering parameters. While it is read-only in nature (retrieving analytics data), the arbitrary/raw query execution pattern with flexible parameters places it in the Execute category rather than simple Read. Misuse could result in large data exfiltration or unintended API quota exhaustion, warranting medium severity.

From the tool's definition 'Run raw GA4 report' — executes an arbitrary report query against GA4 with optional dimension/metric filters and ordering

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ga4_run_report_raw Rate-limited

ga4_run_report_raw 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": {
    "ga4_run_report_raw": {
      "limits": [
        {
          "counter": "ga4_run_report_raw_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 SEO Analytics MCP, so you can run agents against it safely.

FAQ

Questions about ga4_run_report_raw

What does the ga4_run_report_raw tool do? +

Run raw GA4 report with optional dimension/metric filters and ordering. It is categorised as a Execute tool in the SEO Analytics MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ga4_run_report_raw? +

Register the SEO Analytics MCP server in PolicyLayer and add a rule for ga4_run_report_raw: 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 SEO Analytics MCP. Nothing to install.

What risk level is ga4_run_report_raw? +

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

Can I rate-limit ga4_run_report_raw? +

Yes. Add a rate_limit block to the ga4_run_report_raw 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 ga4_run_report_raw completely? +

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

ga4_run_report_raw is provided by the SEO Analytics MCP server (jafforgehq/google-analytics-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.