List email campaigns with filtering options
AI agents call get_email_campaigns 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 tool queries and returns a list of email campaigns, applying optional filters to the results. It performs a passive read operation with no capacity to create, modify, delete, or execute external actions. The filtering is applied to the retrieval query only. Consequently, it falls under the Read category with low severity, as misuse would only expose campaign metadata without enabling harmful actions.
From the tool's definition Tool name 'get_email_campaigns' and description 'List email campaigns with filtering options' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
List email campaigns with filtering options. 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_email_campaigns: 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_email_campaigns 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_email_campaigns 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_email_campaigns. 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_email_campaigns 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 →