Get detailed analytics for a specific campaign including recipient-level data
AI agents call get_campaign_analytics 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 retrieves and queries analytics information for a campaign. It performs no side effects, does not modify data, does not execute code or trigger external operations, and does not involve financial transactions. It is a straightforward read operation that fetches analytics summaries and recipient-level data from the Brevo platform.
From the tool's definition Tool name 'get_campaign_analytics' and description 'Get detailed analytics for a specific campaign including recipient-level data' indicate retrieval of existing analytics data without modification or execution of external operations.
Attacks that exploit this kind of access
Get detailed analytics for a specific campaign including recipient-level data. 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_analytics: 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_analytics 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_analytics 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_analytics. 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_analytics 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 →