get_device_report
AI agents call get_device_report 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 is part of Google Analytics 4 data retrieval suite focused on reporting. The naming convention 'get_device_report' clearly indicates querying/fetching device-related analytics data without modification, deletion, or financial impact. The consistent pattern across all sibling tools confirms this is a reporting/analytics read operation.
From the tool's definition Tool name 'get_device_report' and its position among sibling tools (compare_periods, get_acquisition_report, get_available_metrics, get_events_report, get_geographic_report, get_page_performance, get_property_details, get_realtime_events,…
Attacks that exploit this kind of access
get_device_report. 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_device_report: 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_device_report 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_device_report 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_device_report. 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_device_report 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 →