Launch a draft campaign on Meta (Facebook/Instagram). THIS IS THE MONEY ENDPOINT — it creates real ads on the user's Meta ad account and immediately begins spending their budget. Stored Meta credentials are auto-resolved when available. Set launch_all_variants=true to launch every creative varian...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Zuckerbot server.
Free to start. No card required.
AI agents invoke zuckerbot_launch_campaign to trigger processes or run actions in Zuckerbot. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
zuckerbot_launch_campaign can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"zuckerbot_launch_campaign": {
"limits": [
{
"counter": "zuckerbot_launch_campaign_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Zuckerbot policy for all 59 tools.
These attack patterns abuse exactly the kind of access zuckerbot_launch_campaign gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Launch a draft campaign on Meta (Facebook/Instagram). THIS IS THE MONEY ENDPOINT — it creates real ads on the user's Meta ad account and immediately begins spending their budget. Stored Meta credentials are auto-resolved when available. Set launch_all_variants=true to launch every creative variant as separate ads for A/B testing (Meta auto-optimizes for the winner). Always confirm the user has budget available and Meta is connected (zuckerbot_meta_status) before calling.. It is categorised as a Execute tool in the Zuckerbot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Zuckerbot MCP server in PolicyLayer and add a rule for zuckerbot_launch_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_launch_campaign is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the zuckerbot_launch_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_launch_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_launch_campaign is provided by the Zuckerbot MCP server (zuckerbot-mcp). 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.