get_realtime_traffic_sources
AI agents call get_realtime_traffic_sources 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.
This tool retrieves real-time traffic source data from Google Analytics 4. It performs a read operation with no side effects—it queries existing analytics data without modifying, deleting, or executing code. The blast radius is low as misuse would only expose analytics insights, not compromise systems or data integrity.
From the tool's definition Tool name 'get_realtime_traffic_sources' combined with sibling tools that are all retrieval operations (get_*, compare_*) and server description stating 'historical reporting, real-time activity monitoring' with metrics like 'traffic summaries' and 'user…
Attacks that exploit this kind of access
get_realtime_traffic_sources. 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_traffic_sources: 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_traffic_sources 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_traffic_sources 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_traffic_sources. 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_traffic_sources 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 →