AI agents use create_ad to create or update resources in Vk Ads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vk Ads environment.
An AI agent can call create_ad faster than any human can review — one bad instruction and it creates or modifies resources in Vk Ads by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Создать объявление (banner) VK Ads в группе (ad_group): textblocks, urls, content (медиа-id). It is categorised as a Write tool in the Vk Ads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vk Ads MCP server in PolicyLayer and add a rule for create_ad: 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 Vk Ads. Nothing to install.
create_ad is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_ad 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 create_ad. 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.
create_ad is provided by the Vk Ads MCP server (theyahia/vk-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.