get_device_analysis
AI agents call get_device_analysis to retrieve information from Ya Metrics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve device analytics data from Yandex Metrika, consistent with other read-only reporting tools on this server. No description was provided, which slightly lowers confidence, but the naming pattern and server context strongly suggest it queries analytics data without modifying or executing operations. No irreversible changes, financial transactions, or code execution are implied.
From the tool's definition Tool name 'get_device_analysis' and context within Yandex Metrika analytics server alongside sibling tools like 'get_account_info', 'get_browsers_report', and other report-retrieval tools. The 'get_' prefix and analytics context indicate data retrieval.
Attacks that exploit this kind of access
get_device_analysis. It is categorised as a Read tool in the Ya Metrics MCP Server, which means it retrieves data without modifying state.
Register the Ya Metrics MCP server in PolicyLayer and add a rule for get_device_analysis: 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 Ya Metrics. Nothing to install.
get_device_analysis 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_analysis 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_analysis. 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_analysis is provided by the Ya Metrics MCP server (mrkhachaturov/ya-metrics-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 →