privacy-verify-range
Verify a range proof. Checks that the committed value is within [min, max] without learning the value. Supply the same binding context used during proof creation.
This record as markdown: /tools/dev-forgesworn-bray/privacy-verify-range.md
What privacy-verify-range does on Nostr Bray
AI agents call privacy-verify-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-verify-range is rated Low
This is a pure cryptographic verification operation with no side effects. It reads and validates proof data against specified constraints without creating, modifying, deleting, executing external operations, or moving money. The tool is read-only in nature and poses minimal risk if misused by an AI agent—worst case it returns an incorrect verification result, but cannot corrupt data or trigger external actions.
From the tool's definition Tool performs verification of a cryptographic range proof: 'Verify a range proof' and 'Checks that the committed value is within [min, max]'.
Attacks that exploit this kind of access
The rule that runs privacy-verify-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-verify-range, this is the rule to start with:
privacy-verify-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-verify-range call is checked against it from then on.
Questions about privacy-verify-range
Verify a range proof. Checks that the committed value is within [min, max] without learning the value. Supply the same binding context used during proof creation. 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-verify-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-verify-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-verify-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-verify-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-verify-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