Get top pages by clicks, impressions, sessions, and conversions.
AI agents call analytics_popularity_snapshot 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 returns existing performance data without modifying, deleting, or executing operations. It has no side effects beyond data retrieval. The 'snapshot' framing and presence of similar read-only analytics tools (ga4_landing_pages) confirm this is a simple fetch/retrieval operation with minimal security risk if misused—an agent querying analytics will only see or return existing metrics.
From the tool's definition Tool retrieves aggregate metrics (clicks, impressions, sessions, conversions) from existing analytics data.
Attacks that exploit this kind of access
Get top pages by clicks, impressions, sessions, and conversions. 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_popularity_snapshot: 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_popularity_snapshot 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_popularity_snapshot 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_popularity_snapshot. 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_popularity_snapshot 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 →