特定ページの前後に閲覧されるページを分析します。ユーザーの回遊パターンの把握に便利です。
AI agents call get_user_journey 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 understand user journey patterns. It retrieves and analyzes existing analytics data without modifying, creating, deleting, or executing external operations. This is a classic Read operation—passive data querying for insight generation, consistent with other sibling tools on the server (get_daily_trend, get_engagement_metrics, etc.).
From the tool's definition The tool description states it 'analyzes pages viewed before and after a specific page' (特定ページの前後に閲覧されるページを分析します), which is a data retrieval and analysis operation.
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_user_journey: 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_user_journey 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_user_journey 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_user_journey. 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_user_journey 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 →