get_traffic_summary
AI agents call get_traffic_summary 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 traffic summary data from Google Analytics 4 without modifying any data or executing external operations. The classification as a reporting tool within a read-focused analytics server, combined with the naming pattern and sibling tools, confirms it is a Read operation with low risk. Confidence is high despite empty description because the context is clear and consistent.
From the tool's definition Tool name 'get_traffic_summary' indicates a query/retrieval operation. Server description emphasizes 'historical reporting' and 'metrics like traffic summaries' as read-only data access.
Attacks that exploit this kind of access
get_traffic_summary. 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_traffic_summary: 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_traffic_summary 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_traffic_summary 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_traffic_summary. 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_traffic_summary 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 →