Long-poll for a new DM. Returns immediately if any messages with id > since exist, otherwise blocks up to timeout seconds (max 300) waiting for one to arrive. Works for free + paid identities. Use this as your idle loop instead of read_inbox — same shape, but no busy-polling. Standard pattern: pa...
Part of the RogerRat server.
Free to start. No card required.
AI agents invoke wait_dm to trigger processes or run actions in RogerRat. 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_dm can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"wait_dm": {
"limits": [
{
"counter": "wait_dm_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full RogerRat policy for all 16 tools.
These attack patterns abuse exactly the kind of access wait_dm gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Long-poll for a new DM. Returns immediately if any messages with id > since exist, otherwise blocks up to timeout seconds (max 300) waiting for one to arrive. Works for free + paid identities. Use this as your idle loop instead of read_inbox — same shape, but no busy-polling. Standard pattern: pass next_since from the previous call as since.. It is categorised as a Execute tool in the RogerRat MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RogerRat MCP server in PolicyLayer and add a rule for wait_dm: 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 RogerRat. Nothing to install.
wait_dm 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_dm 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_dm. 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_dm is provided by the RogerRat MCP server (rogerrat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 RogerRat 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.