New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

group-delete-event

Administratively delete one event from a NIP-29 group with kind 9005. Requires confirm: true.

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/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.

Questions about group-delete-event

What does the group-delete-event tool do? +

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.

How do I enforce a policy on group-delete-event? +

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.

What risk level is group-delete-event? +

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.

Can I rate-limit group-delete-event? +

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.

How do I block group-delete-event completely? +

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.

What MCP server provides group-delete-event? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Nostr Bray's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.