get_new_users_by_source
AI agents call get_new_users_by_source 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 analytics data about new user sources from Yandex Metrika. It queries existing analytics without modifying, deleting, or executing external operations. The 'get_' prefix and context within an analytics reporting server confirm read-only behavior with no side effects. Confidence reduced slightly from 1.0 only because description is empty, but the name and sibling context provide strong evidence.
From the tool's definition Tool name 'get_new_users_by_source' indicates a retrieval operation (get_*). Server description confirms this is an analytics tool for accessing reports (traffic, demographics, etc.).
Attacks that exploit this kind of access
get_new_users_by_source. 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_new_users_by_source: 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_new_users_by_source 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_new_users_by_source 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_new_users_by_source. 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_new_users_by_source 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 →