AI agents use send_channel to create or update resources in Agent Bus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Bus environment.
This tool creates and transmits messages to channel subscribers, which is a Write operation (data creation/modification with reversible effects). Severity is medium because misuse could flood channels, disrupt agent workflows, or send unintended communications to multiple agents, but messages are typically not destructive or irreversible.
From the tool's definition Tool name 'send_channel' and description 'Broadcast a message to every subscriber of a channel' indicate creation/transmission of data to multiple recipients.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Broadcast a message to every subscriber of a channel. It is categorised as a Write tool in the Agent Bus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Bus MCP server in PolicyLayer and add a rule for send_channel: 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 Bus. Nothing to install.
send_channel 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_channel 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_channel. 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_channel is provided by the Agent Bus MCP server (mustaphasteph/agent-bus). 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 →