blossom-verify
Verify all media URLs in a note are still accessible. Pass the note content and get back alive/broken status per URL. Optionally verifies SHA-256 hash integrity for blossom URLs.
This record as markdown: /tools/dev-forgesworn-bray/blossom-verify.md
What blossom-verify does on Nostr Bray
AI agents call blossom-verify 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 blossom-verify is rated Low
This tool retrieves status information about URLs and optionally validates cryptographic hashes. It has no side effects on any system, does not modify data, execute code, or perform destructive operations. The use case is read-only verification/audit of link liveness and integrity.
From the tool's definition Tool performs verification and status checking: 'Verify all media URLs in a note are still accessible' and 'get back alive/broken status per URL'. Optional hash integrity checking is also informational.
Attacks that exploit this kind of access
The rule that runs blossom-verify 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 blossom-verify, this is the rule to start with:
blossom-verify 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 blossom-verify call is checked against it from then on.
Questions about blossom-verify
Verify all media URLs in a note are still accessible. Pass the note content and get back alive/broken status per URL. Optionally verifies SHA-256 hash integrity for blossom URLs. 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 blossom-verify: 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.
blossom-verify 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 blossom-verify 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 blossom-verify. 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.
blossom-verify 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