// SCAN REPORT

Ya Metrics

31 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
31 read-only
31 tools total

Community server · catalogue entry verified 29/06/2026

How to control Ya Metrics ↓

TOOL MAP

What Ya Metrics exposes to your agents

Read (31) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

✕

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Ya Metrics

PolicyLayer is an MCP gateway — it sits between your AI agents and Ya Metrics, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations
{
  "compare_segments": {
    "limits": [
      {
        "counter": "compare_segments_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register Ya Metrics — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON YA METRICS →

Instant setup, no code required.

FULL CATALOGUE

All 31 Ya Metrics tools

READ 31 tools
Read compare_segments compare_segments Read compare_segments_drilldown compare_segments_drilldown Read get_account_info Get basic account and counter information from Yandex Metrika. Read get_browsers_report Get browsers report without accounting for browser version. Read get_content_analytics_articles get_content_analytics_articles Read get_content_analytics_authors get_content_analytics_authors Read get_content_analytics_categories get_content_analytics_categories Read get_content_analytics_sources get_content_analytics_sources Read get_content_analytics_topics get_content_analytics_topics Read get_conversion_rate_by_source_and_landing get_conversion_rate_by_source_and_landing Read get_data_by_time get_data_by_time Read get_device_analysis get_device_analysis Read get_drilldown get_drilldown Read get_ecommerce_performance get_ecommerce_performance Read get_geographical_organic_traffic get_geographical_organic_traffic Read get_goals_conversion get_goals_conversion Read get_mobile_vs_desktop get_mobile_vs_desktop Read get_new_users_by_source get_new_users_by_source Read get_organic_search_performance get_organic_search_performance Read get_page_depth_analysis get_page_depth_analysis Read get_page_performance get_page_performance Read get_regional_data get_regional_data Read get_search_engines_data get_search_engines_data Read get_traffic_sources_types Analyze different types of traffic sources (organic, direct, referral). Read get_user_demographics get_user_demographics Read get_visits get_visits Read get_yandex_direct_experiment get_yandex_direct_experiment Read list_counters list_counters Read list_goals List all conversion goals configured for a counter. Use goal IDs with get_goals_conversion. Read sources_search_phrases Retrieve search phrases and browser information from traffic sources. Read sources_summary Get comprehensive traffic sources overview and summary report.
FAQ

Questions about Ya Metrics

Is the Ya Metrics MCP server safe to use without restrictions? +

The Ya Metrics server is primarily read-only with 31 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Ya Metrics MCP server expose? +

31 tools across 1 categories: Read. 31 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Ya Metrics? +

Register the Ya Metrics MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Ya Metrics tool call.

Deterministic rules across all 31 Ya Metrics tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON YA METRICS →

Instant setup, no code required.

31 Ya Metrics tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.