Launch all tiers in an audience portfolio on Meta. Creates separate Meta campaigns for each tier (prospecting, retargeting, reactivation) using the portfolio's budget allocations and CPA targets. Stored Meta credentials are auto-resolved. Tiers that lack required data (e.g., retargeting without a...
Part of the Zuckerbot server.
Free to start. No card required.
AI agents invoke zuckerbot_launch_portfolio 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_portfolio 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_portfolio": {
"limits": [
{
"counter": "zuckerbot_launch_portfolio_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_portfolio 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 all tiers in an audience portfolio on Meta. Creates separate Meta campaigns for each tier (prospecting, retargeting, reactivation) using the portfolio's budget allocations and CPA targets. Stored Meta credentials are auto-resolved. Tiers that lack required data (e.g., retargeting without a pixel, lookalike without enough seed events) are skipped with a reason.. 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_portfolio: 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_portfolio 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_portfolio 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_portfolio. 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_portfolio 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.