AI agents call analytics_realtime to retrieve information from Access without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only queries against Google Analytics to retrieve usage metrics. There are no side effects, no data modification, no destructive operations, and no financial transactions. The scope is limited to analytics data visibility.
From the tool's definition Tool retrieves 'real-time active user data' from Google Analytics 4 with optional breakdown by country, device, or page. Operations are query-only: 'Get', 'Shows' indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
Get real-time active user data from Google Analytics 4. Shows currently active users on the site, optionally broken down by country, device, or page. Data reflects the last 30 minutes. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for analytics_realtime: 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 Access. Nothing to install.
analytics_realtime 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_realtime 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_realtime. 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_realtime is provided by the Access MCP server (scottpedia0/access). 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 →