Webhook management - create, update, delete webhooks for event notifications
AI agents call webhooks to permanently remove resources in Brevo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports delete operations on webhooks, which cannot be undone. Per the rules, when a tool spans categories, the most severe applies: Destructive > Write. Misuse by an AI agent could silently remove webhook configurations that trigger critical business event notifications, with high blast radius across any integrations depending on those webhooks.
From the tool's definition 'create, update, delete webhooks for event notifications' — the delete operation is irreversible
Attacks that exploit this kind of access
Webhook management - create, update, delete webhooks for event notifications. It is categorised as a Destructive tool in the Brevo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for webhooks: 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.
webhooks is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the webhooks 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 webhooks. 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.
webhooks is provided by the Brevo MCP Server MCP server (samihalawa/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 →