SMS operations - send transactional SMS, manage SMS contacts
AI agents invoke sms to trigger actions in Brevo MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending transactional SMS messages triggers external communications to real recipients, which is an irreversible external operation with potential cost implications and real-world effects. While it also includes contact management (Write), the dominant risk is the ability to send SMS messages at scale to arbitrary phone numbers, which could be misused for spam or harassment.
From the tool's definition 'send transactional SMS' - triggers external SMS message delivery to real phone numbers
Attacks that exploit this kind of access
SMS operations - send transactional SMS, manage SMS contacts. It is categorised as a Execute tool in the Brevo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Brevo MCP Server MCP server in PolicyLayer and add a rule for sms: 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.
sms is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sms 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 sms. 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.
sms 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 →