High Risk →

zuckerbot_portfolio_performance

Fetch live Meta performance and downstream CAPI attribution for a launched audience portfolio. Returns enriched tier rows with ad breakdowns, daily metrics, CPA vs. target comparisons, and autonomous evaluation outputs. Use this to monitor a running portfolio and decide whether to rebalance.

Part of the Zuckerbot server.

zuckerbot_portfolio_performance can trigger actions in Zuckerbot, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ZUCKERBOT →

Free to start. No card required.

AI agents invoke zuckerbot_portfolio_performance 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_portfolio_performance 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "zuckerbot_portfolio_performance": {
      "limits": [
        {
          "counter": "zuckerbot_portfolio_performance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Zuckerbot policy for all 59 tools.

Get this rule live on your own Zuckerbot server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ZUCKERBOT →

View all 59 tools →

These attack patterns abuse exactly the kind of access zuckerbot_portfolio_performance gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so zuckerbot_portfolio_performance only ever does what you allow.

SECURE ZUCKERBOT →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the zuckerbot_portfolio_performance tool do? +

Fetch live Meta performance and downstream CAPI attribution for a launched audience portfolio. Returns enriched tier rows with ad breakdowns, daily metrics, CPA vs. target comparisons, and autonomous evaluation outputs. Use this to monitor a running portfolio and decide whether to rebalance.. 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.

How do I enforce a policy on zuckerbot_portfolio_performance? +

Register the Zuckerbot MCP server in PolicyLayer and add a rule for zuckerbot_portfolio_performance: 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.

What risk level is zuckerbot_portfolio_performance? +

zuckerbot_portfolio_performance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit zuckerbot_portfolio_performance? +

Yes. Add a rate_limit block to the zuckerbot_portfolio_performance 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.

How do I block zuckerbot_portfolio_performance completely? +

Set action: deny in the PolicyLayer policy for zuckerbot_portfolio_performance. 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.

What MCP server provides zuckerbot_portfolio_performance? +

zuckerbot_portfolio_performance 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.

Enforce policy on every Zuckerbot tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.