get_user_demographics
AI agents call get_user_demographics 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 demographic data from Yandex Metrika analytics—a passive read operation with no side effects, data modification, code execution, or financial impact. The confidence is slightly reduced (0.85 rather than 0.95) because the tool description is empty, requiring inference from context; however, the server context and naming pattern strongly indicate read-only analytics access.
From the tool's definition Tool name 'get_user_demographics' indicates data retrieval. Server description states it 'enabling AI assistants to access traffic, content, demographics, conversion, e-commerce, and drill-down reports.' The tool is listed among sibling tools that are all…
Attacks that exploit this kind of access
get_user_demographics. 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_user_demographics: 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_user_demographics 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_user_demographics 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_user_demographics. 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_user_demographics 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 →