compare_periods
AI agents call compare_periods to retrieve information from Google Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server's stated purpose of 'historical reporting' and 'real-time activity monitoring' combined with sibling tools that use 'get_' prefixes and retrieve analytics metrics, compare_periods most likely performs a comparative analysis query on existing Google Analytics data. This is a read-only operation with no side effects, data modification, code execution, or financial impact.
From the tool's definition Tool name 'compare_periods' and sibling tools (get_acquisition_report, get_device_report, get_events_report, get_geographic_report, get_page_performance, get_realtime_events) indicate data retrieval operations.
Attacks that exploit this kind of access
compare_periods. It is categorised as a Read tool in the Google Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Analytics MCP Server MCP server in PolicyLayer and add a rule for compare_periods: 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.
compare_periods 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 compare_periods 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 compare_periods. 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.
compare_periods 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.
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 →