ランディングページ（ユーザーが最初にアクセスしたページ）の分析結果を取得します。
AI agents call get_landing_pages to retrieve information from GA4 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Google Analytics 4 data to analyze landing pages and returns insights without creating, modifying, deleting, executing code, or committing financial transactions. It is a straightforward read operation with minimal risk if misused by an AI agent, as it only accesses existing analytics data.
From the tool's definition Tool name 'get_landing_pages' and description indicate retrieval of analysis results for landing pages where users first accessed the site. The verb 'get' and 'retrieve' (取得) confirm data retrieval with no modification or side effects.
Attacks that exploit this kind of access
ランディングページ（ユーザーが最初にアクセスしたページ）の分析結果を取得します。. It is categorised as a Read tool in the GA4 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GA4 MCP Server MCP server in PolicyLayer and add a rule for get_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 GA4 MCP Server. Nothing to install.
get_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 get_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 get_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.
get_landing_pages is provided by the GA4 MCP Server MCP server (shin-sibainu/ga4-mcp-server). 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 →