send_broadcast
Send a draft broadcast to all subscribed contacts (filtered by its audienceTag). Skips unsubscribed/bounced contacts. Returns sent/failed counts.
This record as markdown: /tools/cloud-easybits-easybits/send-broadcast.md
What send_broadcast does on EasyBits
AI agents use send_broadcast to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why send_broadcast is rated Medium
Creates and sends messages to many contacts reversibly; high blast radius if misused for spam or unauthorized campaigns.
From the tool's definition Send draft broadcast to all subscribed contacts, returns sent/failed counts
Attacks that exploit this kind of access
The rule that runs send_broadcast safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_broadcast, this is the rule to start with:
send_broadcast stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every send_broadcast call is checked against it from then on.
Questions about send_broadcast
Send a draft broadcast to all subscribed contacts (filtered by its audienceTag). Skips unsubscribed/bounced contacts. Returns sent/failed counts. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for send_broadcast: 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 EasyBits. Nothing to install.
send_broadcast 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 send_broadcast 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 send_broadcast. 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.
send_broadcast is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue