privacy-prove-range
Prove a secret value is within [min, max] without revealing the value. Returns a cryptographic range proof that anyone can verify against the commitment. Optional binding context prevents proof transplanting between credentials.
This record as markdown: /tools/dev-forgesworn-bray/privacy-prove-range.md
What privacy-prove-range does on Nostr Bray
AI agents call privacy-prove-range 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-prove-range is rated Low
The tool generates and returns a cryptographic proof based on input parameters. This is a compute-and-return operation analogous to a query or fetch operation. There are no side effects: it does not create persistent data (no Write), execute arbitrary operations (no Execute), delete anything (no Destructive), or move funds (no Financial).
From the tool's definition Tool description states it 'Returns a cryptographic range proof' and 'anyone can verify against the commitment' — this is a read/query operation that retrieves a cryptographic proof without modifying, deleting, or executing external code.
Attacks that exploit this kind of access
The rule that runs privacy-prove-range 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-prove-range, this is the rule to start with:
privacy-prove-range 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-prove-range call is checked against it from then on.
Questions about privacy-prove-range
Prove a secret value is within [min, max] without revealing the value. Returns a cryptographic range proof that anyone can verify against the commitment. Optional binding context prevents proof transplanting between credentials. 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-prove-range: 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-prove-range 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-prove-range 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-prove-range. 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-prove-range 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