向多个 Agent 广播消息,适用于任务协调、状态同步、紧急通知。
AI agents use broadcast_message to create or update resources in Agent-Comm-Hub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent-Comm-Hub environment.
Broadcasting messages creates new data artifacts (messages) in the system and modifies communication state across multiple agents. This is a reversible write operation (messages can be archived, acknowledged, or removed). While it affects multiple recipients, it does not execute code, delete data irreversibly, or move financial resources.
From the tool's definition Tool name 'broadcast_message' and description indicate it sends/transmits messages to multiple agents. The description mentions '向多个 Agent 广播消息' (broadcast message to multiple agents) for 'task coordination, status synchronization, emergency notifications.'…
Attacks that exploit this kind of access
向多个 Agent 广播消息,适用于任务协调、状态同步、紧急通知。. It is categorised as a Write tool in the Agent-Comm-Hub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent-Comm-Hub MCP server in PolicyLayer and add a rule for broadcast_message: 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 Agent-Comm-Hub. Nothing to install.
broadcast_message 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 broadcast_message 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 broadcast_message. 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.
broadcast_message is provided by the Agent-Comm-Hub MCP server (liuboacean/agent-comm-hub). 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 →