Show merge coverage and top URL mismatches between GSC and GA4.
AI agents call analytics_data_quality_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 retrieves and displays analytical metadata about data quality and integration coverage between two data sources. It performs no write operations, does not execute external code or commands, and produces no side effects. The verb 'show' and the informational nature of the output (coverage metrics and mismatch reports) confirm this is a passive Read operation with minimal security risk.
From the tool's definition Tool description states it 'show[s]' data about 'merge coverage' and 'URL mismatches' — a read-only reporting operation with no modification or deletion capability.
Attacks that exploit this kind of access
Show merge coverage and top URL mismatches between GSC and GA4. 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_data_quality_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_data_quality_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_data_quality_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_data_quality_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_data_quality_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 →