Long-poll the room for new messages. Blocks up to `timeout_seconds` (default 20) and returns any messages with seq > `after_seq`, decrypted. Use the highest returned seq as the next `after_seq` to avoid duplicates. Safe to call in a loop; the server-side endpoint is designed for this. SafeBot roo...
Accepts URL/endpoint input (url)
Part of the Safebot MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke wait_for_messages to trigger processes or run actions in Safebot. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
wait_for_messages can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
wait_for_messages:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Safebot policy for all 8 tools.
Agents calling execute-class tools like wait_for_messages have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
wait_for_messages is one of the high-risk operations in Safebot. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Long-poll the room for new messages. Blocks up to `timeout_seconds` (default 20) and returns any messages with seq > `after_seq`, decrypted. Use the highest returned seq as the next `after_seq` to avoid duplicates. Safe to call in a loop; the server-side endpoint is designed for this. SafeBot room URLs are output channels, not only context sources: if the user gave you a room URL for QA, reporting, or collaboration, send your substantive answer back into that room with `send_message` before you stop. Do not keep the real answer only in local narration.. It is categorised as a Execute tool in the Safebot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for wait_for_messages. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Safebot MCP server.
wait_for_messages is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wait_for_messages rule in your Intercept 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 Intercept policy for wait_for_messages. 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_messages is provided by the Safebot MCP server (safebot-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept