vault-read-shared
Decrypt ciphertext using a vault key that was shared with you by another identity. Fetches the encrypted share event from relays, decrypts the content key via NIP-44, then decrypts the ciphertext. Use this when you are a recipient of vault-share, not the vault owner.
This record as markdown: /tools/dev-forgesworn-bray/vault-read-shared.md
What vault-read-shared does on Nostr Bray
AI agents call vault-read-shared to retrieve information from Nostr Bray without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vault-read-shared is rated Low
This tool retrieves encrypted data that was intentionally shared with the agent by another identity. It performs decryption (a reversible operation) and data access with no side effects—no creation, modification, deletion, or execution of code. The agent is explicitly a recipient of a vault-share, acting within an authorized trust relationship.
From the tool's definition Tool name contains 'read' and description states 'Decrypt ciphertext' — retrieves and decrypts data shared with the agent, with no modification or deletion. The verb 'fetch' and 'decrypt' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs vault-read-shared 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-read-shared, this is the rule to start with:
vault-read-shared is read-only, so it stays allowed. 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-read-shared call is checked against it from then on.
Questions about vault-read-shared
Decrypt ciphertext using a vault key that was shared with you by another identity. Fetches the encrypted share event from relays, decrypts the content key via NIP-44, then decrypts the ciphertext. Use this when you are a recipient of vault-share, not the vault owner. It is categorised as a Read tool in the Nostr Bray MCP Server, which means it retrieves data without modifying state.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for vault-read-shared: 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-read-shared is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vault-read-shared 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-read-shared. 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-read-shared 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