AI agents call getEvents to retrieve information from Google Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytics event data from Google Analytics 4 without modifying, deleting, or executing code. It is a read-only operation that queries historical metrics. The blast radius is minimal—worst case, an agent could retrieve analytics data the account already has access to, with no side effects on the data or external systems.
From the tool's definition Tool name 'getEvents' and description 'Get event metrics for a specific date range' indicate data retrieval with no modification. This is consistent with sibling tools like 'getPageViews' and 'getUserBehavior' which are all query/analytics operations.
Documented attack patterns abuse exactly the kind of access getEvents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Analytics, and nothing reaches the server without passing your rules. This is the rule we recommend for getEvents:
{
"version": "1",
"default": "deny",
"tools": {
"getEvents": {}
}
}getEvents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get event metrics for a specific date range. It is categorised as a Read tool in the Google Analytics MCP Server, which means it retrieves data without modifying state.
Register the Google Analytics MCP server in PolicyLayer and add a rule for getEvents: 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. Nothing to install.
getEvents 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 getEvents 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 getEvents. 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.
getEvents is provided by the Google Analytics MCP server (ruchernchong/mcp-server-google-analytics). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Google Analytics tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Google Analytics tools catalogued and risk-classified — across an index of 42,500+ MCP servers.