Get recipient list for a specific campaign
AI agents call get_campaign_recipients to retrieve information from Brevo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it queries and retrieves recipient data without side effects. Severity is medium rather than low because recipient lists can contain personally identifiable information (names, email addresses) that could be sensitive in bulk form, creating privacy and security concerns if exposed to an unauthorized or compromised AI agent.
From the tool's definition Tool name 'get_campaign_recipients' and description 'Get recipient list for a specific campaign' indicate data retrieval with no modification. The action is to fetch/retrieve recipient information.
Attacks that exploit this kind of access
Get recipient list for a specific campaign. It is categorised as a Read tool in the Brevo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for get_campaign_recipients: 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.
get_campaign_recipients is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_campaign_recipients 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 get_campaign_recipients. 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.
get_campaign_recipients 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 →