update_campaign_status · Brevo MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_campaign_status does on Brevo MCP Server

AI agents use update_campaign_status to create or update resources in Brevo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brevo MCP Server environment.

WHY IT NEEDS A POLICY

Why update_campaign_status needs a policy

This tool creates or modifies campaign data reversibly by changing status flags. The blast radius is high because pausing or resuming active email campaigns affects all recipients and campaign performance, potentially disrupting marketing workflows and customer communications.

From the tool's definition Tool description states 'Update campaign status (pause, resume, archive)' — modifies campaign state reversibly. The 'pause' and 'resume' actions are reversible state changes typical of Write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_campaign_status Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_campaign_status": {
      "limits": [
        {
          "counter": "update_campaign_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Brevo MCP Server, so you can run agents against it safely.

FAQ

Questions about update_campaign_status

What does the update_campaign_status tool do? +

Update campaign status (pause, resume, archive). It is categorised as a Write tool in the Brevo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_campaign_status? +

Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for update_campaign_status: 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 Brevo MCP Server. Nothing to install.

What risk level is update_campaign_status? +

update_campaign_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_campaign_status? +

Yes. Add a rate_limit block to the update_campaign_status 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 update_campaign_status completely? +

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

update_campaign_status is provided by the Brevo MCP Server MCP server (mark-o298/brevo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.