get_realtime_pages
AI agents call get_realtime_pages to retrieve information from Google Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and context show it retrieves real-time page data from Google Analytics 4 without modifying, deleting, or executing operations. Real-time monitoring in analytics platforms is typically read-only access to live traffic and user session data. No destructive, financial, or code execution capabilities are indicated.
From the tool's definition Tool name 'get_realtime_pages' and server purpose of 'real-time activity monitoring' and 'historical reporting' indicate data retrieval. Sibling tools all follow read-only patterns (get_*, compare_*). Description is empty, slightly lowering confidence.
Attacks that exploit this kind of access
get_realtime_pages. It is categorised as a Read tool in the Google Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Analytics MCP Server MCP server in PolicyLayer and add a rule for get_realtime_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 Google Analytics MCP Server. Nothing to install.
get_realtime_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_realtime_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_realtime_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_realtime_pages is provided by the Google Analytics MCP Server MCP server (reklis/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 →