Get browsers report without accounting for browser version.
AI agents call get_browsers_report 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 browser analytics data from Yandex Metrika without any capability to modify, delete, or execute operations. It is a straightforward read-only query of existing analytics metrics. The low severity reflects that analytics data access has minimal blast radius—it reveals traffic patterns but cannot be leveraged to damage systems or compromise data integrity.
From the tool's definition Tool name 'get_browsers_report' and description 'Get browsers report' indicate data retrieval. The verb 'get' and 'report' context show this is a query operation that retrieves analytics data without modification.
Attacks that exploit this kind of access
Get browsers report without accounting for browser version. 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_browsers_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 Ya Metrics. Nothing to install.
get_browsers_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_browsers_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_browsers_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_browsers_report 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 →