Return GA4 landing pages with engagement and conversion metrics.
AI agents call ga4_landing_pages 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 existing analytics data from Google Analytics 4 to surface landing page performance metrics. It does not create, modify, delete, or execute external operations; it simply retrieves and aggregates metrics. The blast radius of misuse is minimal—an agent could only over-query or leak performance data, not damage systems or commit transactions.
From the tool's definition Tool returns GA4 landing pages with engagement and conversion metrics—a data retrieval operation with no modification or side effects. The verb 'return' and the query-like nature (fetching pre-computed analytics data) indicate read-only behavior.
Attacks that exploit this kind of access
Return GA4 landing pages with engagement and conversion metrics. 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 ga4_landing_pages: 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.
ga4_landing_pages 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 ga4_landing_pages 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 ga4_landing_pages. 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.
ga4_landing_pages 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 →