generate_bulk_zone_tags
Generate ad serving tags for multiple zones at once
This record as markdown: /tools/adbutler/generate-bulk-zone-tags.md
What generate_bulk_zone_tags does on AdButler
AI agents use generate_bulk_zone_tags to create or update resources in AdButler, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
zone_ids | array | Yes | Array of zone IDs to generate tags for |
Parameters from the server's own tool schema.
Why generate_bulk_zone_tags is rated Medium
This tool generates ad serving tags, which are configuration objects that enable ad delivery. Generation creates new data structures that are deployed to ad zones. While not directly modifying existing zones, tag generation creates reversible outputs used for ad serving infrastructure. The bulk nature increases blast radius—a malicious agent could generate incorrect tags across many zones, disrupting ad serving.
From the tool's definition Tool name 'generate_bulk_zone_tags' and description 'Generate ad serving tags for multiple zones at once' indicates creation/generation of ad serving configuration artifacts (tags).
Attacks that exploit this kind of access
The rule that runs generate_bulk_zone_tags safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdButler, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_bulk_zone_tags, this is the rule to start with:
generate_bulk_zone_tags stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AdButler, apply this rule, and every generate_bulk_zone_tags call is checked against it from then on.
Questions about generate_bulk_zone_tags
Generate ad serving tags for multiple zones at once. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
generate_bulk_zone_tags accepts 1 parameter: zone_ids. Required: zone_ids. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler MCP server in PolicyLayer and add a rule for generate_bulk_zone_tags: 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 AdButler. Nothing to install.
generate_bulk_zone_tags 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 generate_bulk_zone_tags 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 generate_bulk_zone_tags. 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.
generate_bulk_zone_tags is provided by the AdButler MCP server (adbutler/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdButler, and thousands of servers like it.
This server
Across the catalogue