dm-send
Send an encrypted direct message. Accepts any identifier: name, NIP-05, npub, or hex pubkey. Default: NIP-17 gift wrap (most private). Set nip04: true for legacy NIP-04 (only if NIP04_ENABLED=1). Use dm-by-name to search your contacts if you are unsure of the exact identity.
This record as markdown: /tools/dev-forgesworn-bray/dm-send.md
What dm-send does on Nostr Bray
AI agents use dm-send to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why dm-send is rated Medium
dm-send creates and persists a new encrypted message on the Nostr network. This is reversible (messages can be deleted or superseded) and has no destructive or financial impact. It is a Write operation rather than Execute because it does not run arbitrary code or trigger external operations based on message content—it simply delivers a crafted message.
From the tool's definition The tool description states 'Send an encrypted direct message' which creates a new message artifact in the Nostr network. This is a write operation that creates/modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs dm-send safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nostr Bray, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dm-send, this is the rule to start with:
dm-send stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every dm-send call is checked against it from then on.
Questions about dm-send
Send an encrypted direct message. Accepts any identifier: name, NIP-05, npub, or hex pubkey. Default: NIP-17 gift wrap (most private). Set nip04: true for legacy NIP-04 (only if NIP04_ENABLED=1). Use dm-by-name to search your contacts if you are unsure of the exact identity. It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for dm-send: 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 Nostr Bray. Nothing to install.
dm-send 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 dm-send 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 dm-send. 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.
dm-send is provided by the Nostr Bray MCP server (nostr-bray). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nostr Bray, and thousands of servers like it.
This server
Across the catalogue