nip44-encrypt
Encrypt a plaintext string using NIP-44 for a recipient pubkey. Uses the active identity\
This record as markdown: /tools/dev-forgesworn-bray/nip44-encrypt.md
What nip44-encrypt does on Nostr Bray
AI agents invoke nip44-encrypt to trigger actions in Nostr Bray. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why nip44-encrypt is rated High
This tool performs a cryptographic operation (encryption) using the active identity's keys. It is not a simple read or write — it executes a cryptographic process that depends on the active identity and recipient pubkey arguments. Misuse could lead to encrypted messages being sent to unintended recipients or enable covert communication channels, but it does not directly delete data or move money.
From the tool's definition 'Encrypt a plaintext string using NIP-44 for a recipient pubkey. Uses the active identity'
Attacks that exploit this kind of access
The rule that runs nip44-encrypt 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 nip44-encrypt, this is the rule to start with:
nip44-encrypt stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 nip44-encrypt call is checked against it from then on.
Questions about nip44-encrypt
Encrypt a plaintext string using NIP-44 for a recipient pubkey. Uses the active identity\. It is categorised as a Execute tool in the Nostr Bray MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for nip44-encrypt: 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.
nip44-encrypt 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 nip44-encrypt 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 nip44-encrypt. 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.
nip44-encrypt 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.
Across the catalogue