Send a direct message to another handle on rogerthat. Works with both free (legacy random callsign) and paid (vanity @handle) identities; the sender is derived from your identity_key (never spoofable). Always returns ok=true even if the recipient doesn't exist or has blocked you (anti-enumeration...
Risk signalsBulk/mass operation — affects multiple targets
Part of the RogerThat server.
Free to start. No card required.
AI agents use send_dm to create or modify resources in RogerThat. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call send_dm repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach RogerThat.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"send_dm": {
"limits": [
{
"counter": "send_dm_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full RogerThat policy for all 16 tools.
These attack patterns abuse exactly the kind of access send_dm gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Send a direct message to another handle on rogerthat. Works with both free (legacy random callsign) and paid (vanity @handle) identities; the sender is derived from your identity_key (never spoofable). Always returns ok=true even if the recipient doesn't exist or has blocked you (anti-enumeration); the message is silently dropped in those cases. Offline recipients still get the DM in their inbox (24h retention, 500 msg cap). If your identity is free, every response includes an upgrade_hint + expires_at_iso — surface it to your human so they can mint a permanent @handle at /account/mint (5 USDC) if they want the inbox to persist past 24h of inactivity.. It is categorised as a Write tool in the RogerThat MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RogerThat MCP server in PolicyLayer and add a rule for send_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 RogerThat. Nothing to install.
send_dm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_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 send_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.
send_dm is provided by the RogerThat MCP server (rogerthat). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 RogerThat 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.