get_mobile_vs_desktop
AI agents call get_mobile_vs_desktop 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.
This tool retrieves and queries Yandex Metrika analytics data to compare mobile vs. desktop traffic metrics. The server provides read-only access to existing analytics reports without creating, modifying, deleting, or executing operations. The tool name pattern matches other non-destructive analytics getters on the server. No side effects or state changes are implied.
From the tool's definition Tool name 'get_mobile_vs_desktop' and server purpose indicate retrieval of analytics reports comparing device types. The server description explicitly lists 'traffic' and 'drill-down reports' as read-only access capabilities.
Attacks that exploit this kind of access
get_mobile_vs_desktop. 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_mobile_vs_desktop: 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_mobile_vs_desktop 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_mobile_vs_desktop 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_mobile_vs_desktop. 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_mobile_vs_desktop 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 →