Multi-tenant account and user management for enterprise features
AI agents use enterprise to create or update resources in Brevo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brevo MCP Server environment.
Account and user management typically involves reversible write operations such as creating users, updating roles, changing settings, or modifying organizational structures. Multi-tenant scope increases blast radius (potential impact on multiple organizations).
From the tool's definition 'account and user management' indicates the tool creates, modifies, or manages user accounts and organizational settings in a multi-tenant system; 'enterprise features' suggests administrative scope; the description lacks detail on specific operations.
Attacks that exploit this kind of access
Multi-tenant account and user management for enterprise features. It is categorised as a Write tool in the Brevo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for enterprise: 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.
enterprise is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the enterprise 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 enterprise. 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.
enterprise 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 →