AI agents invoke broadcastCampaignToList to trigger actions in Mailmodo. 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.
This tool triggers a broadcast campaign to an entire contact list, causing external operations (mass email sending) to be performed. It is not merely writing data — it actively initiates outbound communications to potentially large numbers of recipients.
From the tool's definition "trigger campaigns to the entire contact list using a single API request"
Attacks that exploit this kind of access
The broadcast campaign API allows the user to trigger campaigns to the entire contact list using a single API request. It is categorised as a Execute tool in the Mailmodo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mailmodo MCP server in PolicyLayer and add a rule for broadcastCampaignToList: 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 Mailmodo. Nothing to install.
broadcastCampaignToList 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 broadcastCampaignToList 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 broadcastCampaignToList. 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.
broadcastCampaignToList is provided by the Mailmodo MCP server (mailmodo/mailmodo-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 →