Update an existing email campaign
AI agents use update_email_campaign 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.
This tool creates or modifies data reversibly, fitting the Write category. Severity is high because an AI agent with misuse could alter active marketing campaigns affecting real recipients, damage sender reputation, or corrupt campaign data—though not causing irreversible deletion or financial transactions.
From the tool's definition Tool name is "update_email_campaign" and description states "Update an existing email campaign". The verb "update" modifies existing campaign data (configuration, content, recipients, schedule, etc.) reversibly.
Attacks that exploit this kind of access
Update an existing email campaign. 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.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for update_email_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 Brevo MCP Server. Nothing to install.
update_email_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 update_email_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 update_email_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.
update_email_campaign 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →