Build a complete Meta campaign from an approved Campaign Architect session. IMPORTANT: dry_run defaults to TRUE. When dry_run=true, returns the exact campaign structure that WOULD be created without calling Meta — safe, free, no side effects. Present this to the customer first. Only set dry_run=f...
Part of the Zuckerbot server.
Free to start. No card required.
AI agents use zuckerbot_create_full_campaign to create or modify resources in Zuckerbot. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call zuckerbot_create_full_campaign repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Zuckerbot.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"zuckerbot_create_full_campaign": {
"limits": [
{
"counter": "zuckerbot_create_full_campaign_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Zuckerbot policy for all 59 tools.
These attack patterns abuse exactly the kind of access zuckerbot_create_full_campaign gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Build a complete Meta campaign from an approved Campaign Architect session. IMPORTANT: dry_run defaults to TRUE. When dry_run=true, returns the exact campaign structure that WOULD be created without calling Meta — safe, free, no side effects. Present this to the customer first. Only set dry_run=false after explicit customer approval. When dry_run=false, creates live Meta objects (campaign + ad sets + ads) in PAUSED state. Videos from ad_factory_jobs get linked for rejection tracking automatically.. It is categorised as a Write tool in the Zuckerbot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zuckerbot MCP server in PolicyLayer and add a rule for zuckerbot_create_full_campaign: 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 Zuckerbot. Nothing to install.
zuckerbot_create_full_campaign 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 zuckerbot_create_full_campaign 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 zuckerbot_create_full_campaign. 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.
zuckerbot_create_full_campaign is provided by the Zuckerbot MCP server (DatalisHQ/zuckerbot-d2fa8661). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Zuckerbot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.