send_message
AI agents use send_message to create or update resources in MCP Agent Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Agent Mail environment.
The tool creates or sends messages within a multi-agent coordination system. While the description is uninformative, the name and server context (message threading, inbox) clearly indicate Write capability—reversible message creation. Severity is medium because misuse could spam, impersonate, or misdirect communications between agents, but without financial or destructive impact.
From the tool's definition Tool name 'send_message' in a coordination layer for coding agents with 'message threading' and 'searchable history' indicates message creation/modification. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
send_message. It is categorised as a Write tool in the MCP Agent Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Agent Mail 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 Agent Mail. 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 Agent Mail MCP server (omelchmichael/mcp_agent_mail). 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 →