list_counters
AI agents call list_counters 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.
The naming convention 'list_' strongly suggests a retrieval operation that queries existing data. Combined with the server's purpose (analytics reporting) and the pattern of sibling tools which all read reports and metrics, this is classified as Read. No side effects or data modification are implied.
From the tool's definition Tool name 'list_counters' indicates a listing/retrieval operation. Server context shows this is a Yandex Metrika analytics service where all sibling tools (get_*, compare_*) are read-only report queries.
Attacks that exploit this kind of access
list_counters. 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 list_counters: 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.
list_counters 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 list_counters 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 list_counters. 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.
list_counters 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 →