Get performance report (Spend, Clicks, Conversions). Supports grouping by Campaign, Date, Device, Gender, Age.
AI agents call get_direct_statistics to retrieve information from Yandex Direct without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
date_to | string | Yes | End date YYYY-MM-DD |
group_by | string | — | How to group data. |
api_token | string | Yes | CRITICAL: Always pass API_TOKEN here. |
date_from | string | Yes | Start date YYYY-MM-DD |
campaign_ids | array | — | Optional: Filter by specific Campaign IDs. |
client_login | string | — | CRITICAL: Always pass CLIENT_LOGIN here if it exists in system prompt. |
Parameters from the server's own tool schema.
The tool only reads and retrieves advertising statistics without modifying account settings, spending money, or executing actions. The data retrieved (spend, clicks, conversions) is historical performance information. While sensitive from a business intelligence perspective, the action itself is non-destructive and non-transactional, making it a Read operation with low severity.
From the tool's definition Tool retrieves performance report data (Spend, Clicks, Conversions) with grouping options. No modification, deletion, or financial transaction occurs. This is a data query operation similar to its sibling 'get_search_queries' and 'get_campaigns_list'.
Attacks that exploit this kind of access
Get performance report (Spend, Clicks, Conversions). Supports grouping by Campaign, Date, Device, Gender, Age. It is categorised as a Read tool in the Yandex Direct MCP Server, which means it retrieves data without modifying state.
get_direct_statistics accepts 6 parameters: date_to, group_by, api_token, date_from, campaign_ids, client_login. Required: date_to, api_token, date_from. The full parameter table on this page comes from the server's own tool schema.
Register the Yandex Direct MCP server in PolicyLayer and add a rule for get_direct_statistics: 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 Yandex Direct. Nothing to install.
get_direct_statistics 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_direct_statistics 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_direct_statistics. 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_direct_statistics is provided by the Yandex Direct MCP server (yandex-direct-mcp-server). 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 →