group-delete-event
Administratively delete one event from a NIP-29 group with kind 9005. Requires confirm: true.
This record as markdown: /tools/dev-forgesworn-bray/group-delete-event.md
What group-delete-event does on Nostr Bray
AI agents call group-delete-event 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 group-delete-event is rated Critical
This tool permanently removes an event from a group, which cannot be undone. Although it requires a confirm flag (a safeguard), the core function is destructive — deletion with no recovery path. In a multi-agent system, accidental or malicious invocation could remove group content irreversibly. This is more severe than Write (which is reversible) and warrants Destructive classification.
From the tool's definition Tool name contains 'delete' and description states 'Administratively delete one event' — this is irreversible removal of data. Operates on a Nostr group (NIP-29) with administrative privilege.
Attacks that exploit this kind of access
The rule that runs group-delete-event 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 group-delete-event, this is the rule to start with:
group-delete-event 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 group-delete-event call is checked against it from then on.
Questions about group-delete-event
Administratively delete one event from a NIP-29 group with kind 9005. Requires confirm: true. 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 group-delete-event: 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.
group-delete-event 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 group-delete-event 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 group-delete-event. 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.
group-delete-event 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