get_content_analytics_categories
AI agents call get_content_analytics_categories 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 content analytics category data from Yandex Metrika. It has no side effects—it queries and returns analytics data only. The 'get_' prefix and context of being an analytics server strongly indicate read-only data retrieval. Confidence is slightly reduced due to empty description, but sibling tool patterns provide strong corroborating evidence.
From the tool's definition Tool name 'get_content_analytics_categories' contains the verb 'get', which retrieves data. Description is empty, but the pattern of sibling tools (all get_* and compare_* functions) on this Yandex Metrika analytics server confirms this is a data retrieval…
Attacks that exploit this kind of access
get_content_analytics_categories. 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_content_analytics_categories: 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_content_analytics_categories 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_content_analytics_categories 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_content_analytics_categories. 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_content_analytics_categories 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 →