Get GA4 traffic acquisition data by source/medium
AI agents call ga4_acquisition_report to retrieve information from MCP Search Analytics Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only (Read category). It queries existing analytics data from Google Analytics 4 to report traffic sources and mediums. No data is created, modified, deleted, or executed. The severity is low because unauthorized access to traffic analytics may reveal business patterns but does not directly enable destructive, financial, or operational harm.
From the tool's definition Tool retrieves GA4 traffic acquisition data by source/medium - a query operation that gathers analytics metrics without modifying any data.
Attacks that exploit this kind of access
Get GA4 traffic acquisition data by source/medium. It is categorised as a Read tool in the MCP Search Analytics Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Search Analytics Server MCP server in PolicyLayer and add a rule for ga4_acquisition_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 MCP Search Analytics Server. Nothing to install.
ga4_acquisition_report 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 ga4_acquisition_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.
Set action: deny in the PolicyLayer policy for ga4_acquisition_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.
ga4_acquisition_report is provided by the MCP Search Analytics Server MCP server (vesivanov/mcp-search-analytics). 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 →