List all conversion goals configured for a counter. Use goal IDs with get_goals_conversion.
AI agents call list_goals 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 and enumerates conversion goals from Yandex Metrika analytics configuration. It is a read-only operation with no side effects—it simply lists data that already exists. The purpose is to fetch goal IDs for use with other tools (get_goals_conversion). There is no data modification, deletion, code execution, or financial impact. This is a straightforward Read category tool with low risk.
From the tool's definition Tool name 'list_goals' and description 'List all conversion goals configured for a counter' indicate a retrieval operation that queries existing configuration data without modifying or deleting anything.
Attacks that exploit this kind of access
List all conversion goals configured for a counter. Use goal IDs with get_goals_conversion. 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_goals: 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_goals 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_goals 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_goals. 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_goals 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 →