Build a valid Google Analytics 4 Data API runReport request body from plain parameters. e.g., input: metrics=[
AI agents call build_ga4_query to retrieve information from Query Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool builds a GA4 API request body for a runReport operation, which is a read/query operation that retrieves analytics data. It does not execute the request itself (it only constructs the payload), and the sibling tools (aggregate_rows, format_analytics_metric, parse_filter_expression) further confirm this is a data-retrieval pipeline with no write or destructive side effects.
From the tool's definition 'Build a valid Google Analytics 4 Data API runReport request body from plain parameters' — constructs a query/report request for reading analytics data
Attacks that exploit this kind of access
Build a valid Google Analytics 4 Data API runReport request body from plain parameters. e.g., input: metrics=[. It is categorised as a Read tool in the Query Analytics MCP Server, which means it retrieves data without modifying state.
Register the Query Analytics MCP server in PolicyLayer and add a rule for build_ga4_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 Query Analytics. Nothing to install.
build_ga4_query 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 build_ga4_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.
Set action: deny in the PolicyLayer policy for build_ga4_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.
build_ga4_query is provided by the Query Analytics MCP server (josephtandle/google-analytics-mcp-mcp). 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 →