blossom-delete

Delete a blob from a blossom media server by SHA-256 hash.

SERVERNostr Bray SOURCEnostr-bray

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-bray/blossom-delete.md

WHAT IT DOES

What blossom-delete does on Nostr Bray

AI agents call blossom-delete to permanently remove resources in Nostr Bray, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why blossom-delete is rated Critical

This tool performs an irreversible deletion operation on media files stored on a Blossom server. Once a blob is deleted by hash, it cannot be recovered unless separately backed up. In the context of an AI agent with MCP access, misuse could result in loss of user media assets.

From the tool's definition The tool description explicitly states "Delete a blob from a blossom media server by SHA-256 hash." The verb "Delete" combined with the irreversible nature of removing media from a server clearly places this in the Destructive category.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs blossom-delete 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-delete, this is the rule to start with:

blossom-delete Hidden

blossom-delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "blossom-delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every blossom-delete call is checked against it from then on.

FAQ

Questions about blossom-delete

What does the blossom-delete tool do? +

Delete a blob from a blossom media server by SHA-256 hash. It is categorised as a Destructive tool in the Nostr Bray MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on blossom-delete? +

Register the Nostr Bray MCP server in PolicyLayer and add a rule for blossom-delete: 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.

What risk level is blossom-delete? +

blossom-delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit blossom-delete? +

Yes. Add a rate_limit block to the blossom-delete 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.

How do I block blossom-delete completely? +

Set action: deny in the PolicyLayer policy for blossom-delete. 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.

What MCP server provides blossom-delete? +

blossom-delete 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.

KEEP EXPLORING

More on Nostr Bray, and thousands of servers like it.

This server

All 240 Nostr Bray tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →