comms_send_campaign
Execute a draft or scheduled campaign. Sends messages to all matching recipients asynchronously, skipping recipients with email opt-out or bounced addresses (logged as "skipped"). Campaign must be in draft or scheduled status. Returns immediately — use comms_get_campaign to track progress (sent/d...
This record as markdown: /tools/com-servicialo-mcp-server/comms-send-campaign.md
What comms_send_campaign does on Servicialo
AI agents invoke comms_send_campaign to trigger actions in Servicialo. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey | string | — | |
confirm | boolean | Yes | |
orgSlug | string | Yes | |
campaignId | string | Yes |
Parameters from the server's own tool schema.
Why comms_send_campaign is rated High
Triggers mass message delivery to many recipients; irreversible external communication action.
From the tool's definition Sends messages to all matching recipients asynchronously
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs comms_send_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comms_send_campaign, this is the rule to start with:
comms_send_campaign stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every comms_send_campaign call is checked against it from then on.
Questions about comms_send_campaign
Execute a draft or scheduled campaign. Sends messages to all matching recipients asynchronously, skipping recipients with email opt-out or bounced addresses (logged as "skipped"). Campaign must be in draft or scheduled status. Returns immediately — use comms_get_campaign to track progress (sent/delivered/opened/clicked update via provider webhooks). Requires confirm: true. It is categorised as a Execute tool in the Servicialo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
comms_send_campaign accepts 4 parameters: apiKey, confirm, orgSlug, campaignId. Required: confirm, orgSlug, campaignId. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for comms_send_campaign: 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 Servicialo. Nothing to install.
comms_send_campaign 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 comms_send_campaign 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 comms_send_campaign. 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.
comms_send_campaign is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
Across the catalogue