Get basic account and counter information from Yandex Metrika.
AI agents call get_account_info 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 account and counter metadata from Yandex Metrika analytics. There is no indication it modifies data, executes operations, deletes resources, or moves money. It is a straightforward information retrieval operation. Severity is low because account metadata exposure is typically low-impact, though it could inform further reconnaissance if combined with other tools.
From the tool's definition Tool name 'get_account_info' and description 'Get basic account and counter information' indicate a retrieval operation with no modification or side effects. This aligns with the Read category pattern of fetching metadata.
Attacks that exploit this kind of access
Get basic account and counter information from Yandex Metrika. 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_account_info: 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_account_info 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_account_info 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_account_info. 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_account_info 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 →