Get list of all direct campaigns with their ID, status and remaining budget. Useful to get CampaignId for filtering.
AI agents call get_campaigns_list 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 |
|---|---|---|---|
api_token | string | Yes | CRITICAL: Always pass API_TOKEN here. |
client_login | string | — | CRITICAL: Always pass CLIENT_LOGIN here if it exists in system prompt. |
Parameters from the server's own tool schema.
This is a straightforward query/list operation that retrieves campaign metadata from Yandex Direct. It has no side effects, does not modify data, and does not execute code or transactions. The purpose is to fetch information for filtering in subsequent operations. The 'remaining budget' field is read-only metadata, not a financial transaction or operation that moves money.
From the tool's definition Tool description states 'Get list of all direct campaigns' - a retrieval operation with no modification. Returns campaign ID, status, and remaining budget information only.
Attacks that exploit this kind of access
Get list of all direct campaigns with their ID, status and remaining budget. Useful to get CampaignId for filtering. It is categorised as a Read tool in the Yandex Direct MCP Server, which means it retrieves data without modifying state.
get_campaigns_list accepts 2 parameters: api_token, client_login. Required: api_token. 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_campaigns_list: 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_campaigns_list 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_campaigns_list 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_campaigns_list. 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_campaigns_list 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 →