GOOGLESUPER_BATCH_RUN_REPORTS

Tool to return multiple analytics data reports in a batch. Use when you need to fetch multiple reports for one GA4 property in a single request.

SERVERGoogle Super SOURCEgooglesuper
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-batch-run-reports.md

What GOOGLESUPER_BATCH_RUN_REPORTS does on Google Super

AI agents call GOOGLESUPER_BATCH_RUN_REPORTS to retrieve information from Google Super without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
property string Required. The property resource name. Format: properties/{property_id}
requests array Required. Up to 5 individual RunReportRequest objects.

Parameters from the server's own tool schema.

Why GOOGLESUPER_BATCH_RUN_REPORTS is rated Low

This tool retrieves analytics data reports from Google Analytics 4. It only reads/fetches data with no side effects, modifications, or destructive operations. The blast radius is low since it only reads analytics data.

From the tool's definition 'return multiple analytics data reports in a batch' and 'fetch multiple reports for one GA4 property'

Questions about GOOGLESUPER_BATCH_RUN_REPORTS

What does the GOOGLESUPER_BATCH_RUN_REPORTS tool do? +

Tool to return multiple analytics data reports in a batch. Use when you need to fetch multiple reports for one GA4 property in a single request. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.

What parameters does GOOGLESUPER_BATCH_RUN_REPORTS accept? +

GOOGLESUPER_BATCH_RUN_REPORTS accepts 2 parameters: property, requests. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_BATCH_RUN_REPORTS? +

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

What risk level is GOOGLESUPER_BATCH_RUN_REPORTS? +

GOOGLESUPER_BATCH_RUN_REPORTS is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit GOOGLESUPER_BATCH_RUN_REPORTS? +

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

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

GOOGLESUPER_BATCH_RUN_REPORTS is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Google Super, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Super's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.