Merge normalized GSC + GA4 page metrics into one dataset.
AI agents call analytics_merge_page_metrics 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 merges/combines data from two analytics sources (Google Search Console and Google Analytics 4) into a unified dataset. It is a read/query operation that retrieves and normalizes existing metrics without creating, modifying, or deleting any data. The blast radius is low as misuse would only result in fetching or combining analytics data.
From the tool's definition Merge normalized GSC + GA4 page metrics into one dataset
Attacks that exploit this kind of access
Merge normalized GSC + GA4 page metrics into one dataset. 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_merge_page_metrics: 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_merge_page_metrics 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_merge_page_metrics 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_merge_page_metrics. 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_merge_page_metrics 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 →