Send a message to another Claude session (by name or ID) or to a channel.
AI agents use send_message to create or update resources in MCP channel — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP channel environment.
send_message creates new data (messages) in a communication system. It is reversible (messages can typically be deleted or ignored by recipients) and has no direct destructive or financial impact. While it enables inter-agent communication that could be misused for prompt injection or social engineering between agents, the tool itself only writes messages.
From the tool's definition Tool description states it 'Send a message to another Claude session (by name or ID) or to a channel.' The verb 'send' with 'message' indicates creation/modification of communication data.
Attacks that exploit this kind of access
Send a message to another Claude session (by name or ID) or to a channel. It is categorised as a Write tool in the MCP channel MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP channel MCP server in PolicyLayer and add a rule for send_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 MCP channel. Nothing to install.
send_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 send_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 send_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.
send_message is provided by the MCP channel MCP server (rmarquis/mcp-channel). 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 →