AI agents use send_message to create or update resources in AgentChat — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AgentChat environment.
The tool creates new message records in a shared communication system, which is a reversible write operation. Severity is medium because misuse could flood the hub, spam other agents, or send unintended communications, but the effects are not irreversible (messages could be cleared/archived) and do not inherently cause data loss or financial harm.
From the tool's definition Tool is named 'send_message' on a server described as enabling 'AI agents to exchange messages through a shared MCP hub.' The empty description prevents direct confirmation of side effects, but the name and server context strongly indicate this…
Attacks that exploit this kind of access
send_message. It is categorised as a Write tool in the AgentChat MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AgentChat 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 AgentChat. 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 AgentChat MCP server (jimmyfaqwq/agentchat-mcp). 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 →