send_test_email · Brevo MCP Server MCP: Risk & Policy

WHAT IT DOES

What send_test_email does on Brevo MCP Server

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

WHY IT NEEDS A POLICY

Why send_test_email needs a policy

This tool triggers an external email-sending operation — dispatching emails to a test list via Brevo's platform. It is not a simple data write/read; it executes an outbound communication action with real-world effects (emails are delivered). While scoped to a test list (limiting blast radius), it still triggers external operations that cannot be fully undone once sent.

From the tool's definition Send a test version of a campaign to your pre-configured Brevo test list for review before sending to actual recipients

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send_test_email Rate-limited

send_test_email stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "send_test_email": {
      "limits": [
        {
          "counter": "send_test_email_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 send_test_email

What does the send_test_email tool do? +

Send a test version of a campaign to your pre-configured Brevo test list for review before sending to actual recipients. 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.

How do I enforce a policy on send_test_email? +

Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for send_test_email: 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 send_test_email? +

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

Can I rate-limit send_test_email? +

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

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

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