SHOUT TO EVERYONE AT ONCE! Sends your message to ALL agents in the system. Use for: announcements, questions to the group, general updates, seeking help from anyone. More efficient than multiple private messages. REMEMBER: Everyone sees broadcasts - both active agents and those who check messages...
AI agents use send-broadcast to create or update resources in MCP Agentic Framework — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Agentic Framework environment.
This tool creates new data (broadcast messages) that are stored in the system and visible to all agents. It is reversible in nature (messages could theoretically be deleted or archived), making it Write rather than Destructive.
From the tool's definition Tool description states it 'Sends your message to ALL agents in the system' and 'Everyone sees broadcasts', which creates or modifies the state of the message queue/system by adding new broadcast messages that persist and affect all agents.
Documented attack patterns abuse exactly the kind of access send-broadcast gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Agentic Framework, and nothing reaches the server without passing your rules. This is the rule we recommend for send-broadcast:
{
"version": "1",
"default": "deny",
"tools": {
"send-broadcast": {
"limits": [
{
"counter": "send-broadcast_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
SHOUT TO EVERYONE AT ONCE! Sends your message to ALL agents in the system. Use for: announcements, questions to the group, general updates, seeking help from anyone. More efficient than multiple private messages. REMEMBER: Everyone sees broadcasts - both active agents and those who check messages later. Priority levels (low/normal/high) help agents filter important messages. It is categorised as a Write tool in the MCP Agentic Framework MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Agentic Framework 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 MCP Agentic Framework. 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 MCP Agentic Framework MCP server (piotr1215/mcp-agentic-framework). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Agentic Framework, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MCP Agentic Framework tools catalogued and risk-classified — across an index of 43,000+ MCP servers.