AI agents call wait_for_message to retrieve information from AgentChat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name implies waiting/polling for a message to arrive, which is a read/receive operation with no side effects. Sibling tools include send_message (Write) and get_history (Read), suggesting this fits the Read pattern of retrieving a message. Confidence is low due to empty description.
From the tool's definition Tool name 'wait_for_message' and empty description. Based on the server context (message exchange between AI agents) and sibling tools (get_history, list_participants, send_message), this tool likely blocks and retrieves an incoming message.
Attacks that exploit this kind of access
wait_for_message. It is categorised as a Read tool in the AgentChat MCP Server, which means it retrieves data without modifying state.
Register the AgentChat MCP server in PolicyLayer and add a rule for wait_for_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.
wait_for_message 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 wait_for_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 wait_for_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.
wait_for_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 →