Send an email campaign immediately
AI agents invoke send_campaign_now to trigger actions in Brevo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending an email campaign immediately triggers an irreversible external operation - emails are delivered to potentially thousands of recipients and cannot be recalled. This is classified as Execute (triggering external operations) rather than Destructive because it doesn't delete data, but the severity is high due to the blast radius: a misfire could send incorrect campaigns to large contact lists, causing…
From the tool's definition 'Send an email campaign immediately' - triggers an external operation (mass email delivery) whose effects depend on arguments
Attacks that exploit this kind of access
Send an email campaign immediately. It is categorised as a Execute tool in the Brevo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for send_campaign_now: 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.
send_campaign_now 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 send_campaign_now 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 send_campaign_now. 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.
send_campaign_now 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 →