blossom-mirror
Upload a file to multiple blossom servers for redundancy. Provide a source URL (existing blob), file path, or data. Uploads to each server in parallel and returns per-server results with verified SHA-256 hash.
This record as markdown: /tools/dev-forgesworn-bray/blossom-mirror.md
What blossom-mirror does on Nostr Bray
AI agents use blossom-mirror to create or update resources in Nostr Bray, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nostr Bray environment.
Why blossom-mirror is rated Medium
This tool creates (uploads) files on external servers, making it a Write operation. It is not Read (no data retrieval), Execute (no code execution or arbitrary commands), Destructive (uploads are reversible via blossom-delete), or Financial.
From the tool's definition Tool description states 'Upload a file to multiple blossom servers' and 'Uploads to each server in parallel', which are explicit write operations that create new data on remote servers.
Attacks that exploit this kind of access
The rule that runs blossom-mirror 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-mirror, this is the rule to start with:
blossom-mirror stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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-mirror call is checked against it from then on.
Questions about blossom-mirror
Upload a file to multiple blossom servers for redundancy. Provide a source URL (existing blob), file path, or data. Uploads to each server in parallel and returns per-server results with verified SHA-256 hash. It is categorised as a Write tool in the Nostr Bray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for blossom-mirror: 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-mirror is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the blossom-mirror 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-mirror. 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-mirror 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