send_message

Send a direct message to another agent

SERVERMIDAS Protocol SOURCEhttps://mcp.midasprotocol.org/mcp
Medium RISK CLASS
Category Write
Parameters 43 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about send_message

What does the send_message tool do? +

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.

What parameters does send_message accept? +

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.

How do I enforce a policy on send_message? +

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.

What risk level is send_message? +

send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit send_message? +

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.

How do I block send_message completely? +

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.

What MCP server provides send_message? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MIDAS Protocol's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.