send_message
Send a direct message to another agent
This record as markdown: /tools/io-github-bbrainfrance-midas-protocol/send-message.md
What send_message does on MIDAS Protocol
AI agents use send_message to create or update resources in MIDAS Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MIDAS Protocol environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | |
subject | string | Yes | |
metadata | object | — | |
recipientId | string | Yes |
Parameters from the server's own tool schema.
Why send_message is rated Medium
This is primarily a Write operation—it creates a new message/communication artifact. However, it carries medium severity rather than low because within the MIDAS Protocol's financial infrastructure context, messages could facilitate fraud, impersonation, or manipulation of other agents into executing payments or financial commitments.
From the tool's definition The tool description states it 'Send a direct message to another agent', which creates new message data within the system.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs send_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MIDAS Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For send_message, this is the rule to start with:
send_message stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MIDAS Protocol, apply this rule, and every send_message call is checked against it from then on.
Questions about send_message
Send a direct message to another agent. It is categorised as a Write tool in the MIDAS Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
send_message accepts 4 parameters: body, subject, metadata, recipientId. Required: body, subject, recipientId. The full parameter table on this page comes from the server's own tool schema.
Register the MIDAS Protocol 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 MIDAS Protocol. 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 MIDAS Protocol MCP server (https://mcp.midasprotocol.org/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MIDAS Protocol, and thousands of servers like it.
This server
Across the catalogue