privacy-read-proof
Fetch and verify range proof events from relays. Returns a list of proofs with their verification status, labels, ranges, and subject pubkeys.
This record as markdown: /tools/dev-forgesworn-bray/privacy-read-proof.md
What privacy-read-proof does on Nostr Bray
AI agents call privacy-read-proof 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 privacy-read-proof is rated Low
This tool retrieves and queries existing proof events from Nostr relays, then performs verification on them. The operation is read-only: it fetches data and returns information without creating, modifying, deleting, or executing external commands. The verification is a local computation on retrieved data. No data is written, deleted, or financial transactions are involved.
From the tool's definition Tool name contains 'read' and description states 'Fetch and verify range proof events from relays. Returns a list of proofs' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs privacy-read-proof 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 privacy-read-proof, this is the rule to start with:
privacy-read-proof 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 privacy-read-proof call is checked against it from then on.
Questions about privacy-read-proof
Fetch and verify range proof events from relays. Returns a list of proofs with their verification status, labels, ranges, and subject pubkeys. 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 privacy-read-proof: 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.
privacy-read-proof 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 privacy-read-proof 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 privacy-read-proof. 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.
privacy-read-proof 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