get_conversion_rate_by_source_and_landing
AI agents call get_conversion_rate_by_source_and_landing 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 conversion rate analytics data from Yandex Metrika. The 'get_' prefix and positioning alongside other analytics retrieval functions (get_browsers_report, get_content_analytics_*) indicate this is a query operation that accesses but does not modify, execute commands, or delete data. No side effects are implied.
From the tool's definition Tool name contains 'get_conversion_rate_by_source_and_landing' indicating data retrieval. Server description states it 'enabling AI assistants to access traffic, content, demographics, conversion, e-commerce, and drill-down reports' with no mention of…
Attacks that exploit this kind of access
get_conversion_rate_by_source_and_landing. 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_conversion_rate_by_source_and_landing: 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_conversion_rate_by_source_and_landing 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_conversion_rate_by_source_and_landing 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_conversion_rate_by_source_and_landing. 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_conversion_rate_by_source_and_landing 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 →