run_custom_realtime_report · Google Analytics MCP Server MCP

WHAT IT DOES

What run_custom_realtime_report does on Google Analytics MCP Server

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

A 'run_custom_realtime_report' tool likely permits execution of user-specified queries or report configurations against live GA4 data. While the tool appears read-only in intent (reporting), the 'run' and 'custom' qualifiers indicate the agent can execute arbitrary logic whose results depend on parameters. This contrasts with sibling tools which appear to run fixed, pre-defined reports.

From the tool's definition Tool name 'run_custom_realtime_report' suggests execution of arbitrary or custom queries against Google Analytics 4 real-time data. The 'run' verb indicates code/query execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_custom_realtime_report Rate-limited

run_custom_realtime_report 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": {
    "run_custom_realtime_report": {
      "limits": [
        {
          "counter": "run_custom_realtime_report_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 Google Analytics MCP Server, so you can run agents against it safely.

FAQ

Questions about run_custom_realtime_report

What does the run_custom_realtime_report tool do? +

run_custom_realtime_report. It is categorised as a Execute tool in the Google Analytics MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_custom_realtime_report? +

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

What risk level is run_custom_realtime_report? +

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

Can I rate-limit run_custom_realtime_report? +

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

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

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