vault-encrypt
Encrypt content using a content key derived from the active identity for a given tier and epoch. No network access — purely local cryptography. Returns the ciphertext, tier, and epoch used.
This record as markdown: /tools/dev-forgesworn-bray/vault-encrypt.md
What vault-encrypt does on Nostr Bray
AI agents invoke vault-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 vault-encrypt is rated High
Encryption is a computational/transformation operation that executes local cryptography. It is not a simple read (it transforms data), not a write (nothing is stored), and not destructive or financial. Execute is the most appropriate category for a tool that runs a cryptographic algorithm and returns derived ciphertext.
From the tool's definition 'Encrypt content using a content key derived from the active identity for a given tier and epoch' — performs a cryptographic operation (key derivation + encryption) locally
Attacks that exploit this kind of access
The rule that runs vault-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 vault-encrypt, this is the rule to start with:
vault-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 vault-encrypt call is checked against it from then on.
Questions about vault-encrypt
Encrypt content using a content key derived from the active identity for a given tier and epoch. No network access — purely local cryptography. Returns the ciphertext, tier, and epoch used. 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 vault-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.
vault-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 vault-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 vault-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.
vault-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