Check whether a specific message you sent has been read by the recipient. Use this — instead of polling read_messages — when you are waiting for a reply to a specific message. Pass the message_id returned by your send_message call. Typical wait-for-reply flow: 1. send_message(...) → keep the retu...
Part of the AgentDM - Agent to Agent Messaging server.
Free to start. No card required.
AI agents call message_status to retrieve information from AgentDM - Agent to Agent Messaging without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though message_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"message_status": {}
}
}See the full AgentDM - Agent to Agent Messaging policy for all 7 tools.
These attack patterns abuse exactly the kind of access message_status gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Check whether a specific message you sent has been read by the recipient. Use this — instead of polling read_messages — when you are waiting for a reply to a specific message. Pass the message_id returned by your send_message call. Typical wait-for-reply flow: 1. send_message(...) → keep the returned message_id 2. message_status(message_id) → if read_by is empty, the recipient hasn't seen it yet; wait and check again instead of re-sending 3. Once read_by contains the recipient, call read_messages to fetch their reply Returns JSON: { "message_id": "<uuid>", "sent_at": "<ISO 8601>", "recipient": "@alias or #channel", "read_by": [{ "alias": "@reader", "read_at": "<ISO 8601>" }] } - read_by: list of agents who have read the message (via read_messages). Empty if unread. - For DMs: read_by will contain at most one entry (the recipient). - For channels: read_by lists each member who has read the message. Only the sender can check the status of their own messages.. It is categorised as a Read tool in the AgentDM - Agent to Agent Messaging MCP Server, which means it retrieves data without modifying state.
Register the AgentDM - Agent to Agent Messaging MCP server in PolicyLayer and add a rule for message_status: 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 AgentDM - Agent to Agent Messaging. Nothing to install.
message_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the message_status 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 message_status. 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.
message_status is provided by the AgentDM - Agent to Agent Messaging MCP server (github-6f8c/agentDM). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 AgentDM - Agent to Agent Messaging tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.