Compare current vs previous period to surface gainers and decliners.
AI agents call analytics_trend_report to retrieve information from SEO Analytics MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and analyzes existing analytics data to generate comparative reports. It performs no side effects: it does not create, modify, delete, or irreversibly change data, nor does it execute code or trigger external operations. The output is a read-only trend analysis.
From the tool's definition Tool description states it "Compare[s] current vs previous period to surface gainers and decliners" — a retrieval and analysis operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Compare current vs previous period to surface gainers and decliners. It is categorised as a Read tool in the SEO Analytics MCP MCP Server, which means it retrieves data without modifying state.
Register the SEO Analytics MCP server in PolicyLayer and add a rule for analytics_trend_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 SEO Analytics MCP. Nothing to install.
analytics_trend_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 analytics_trend_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 analytics_trend_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.
analytics_trend_report is provided by the SEO Analytics MCP server (jafforgehq/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 →