label-remove
Delete a label event via kind 5 deletion. Only works for labels you authored.
This record as markdown: /tools/dev-forgesworn-bray/label-remove.md
What label-remove does on Nostr Bray
AI agents call label-remove 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.
Why label-remove is rated Critical
This tool permanently deletes label events authored by the user. Deletion is irreversible and cannot be undone, fitting the Destructive category. Severity is high because deletion of labels could affect identity/reputation systems, trust networks, or social signals in the Nostr ecosystem, impacting multiple downstream references.
From the tool's definition Tool description states "Delete a label event" and explicitly mentions "kind 5 deletion", which in the Nostr protocol is a deletion event. The description confirms irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs label-remove 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 label-remove, this is the rule to start with:
label-remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Nostr Bray, apply this rule, and every label-remove call is checked against it from then on.
Questions about label-remove
Delete a label event via kind 5 deletion. Only works for labels you authored. 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.
Register the Nostr Bray MCP server in PolicyLayer and add a rule for label-remove: 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.
label-remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the label-remove 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 label-remove. 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.
label-remove 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.
Across the catalogue