group-remove-user
Remove a user from a NIP-29 group (kind 9001 admin event).
This record as markdown: /tools/dev-forgesworn-bray/group-remove-user.md
What group-remove-user does on Nostr Bray
AI agents call group-remove-user 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-remove-user is rated Critical
Removing a user from a group is a destructive, non-reversible action: the user loses access and membership. This is an administrative operation with significant social impact, especially in a trust-aware social system where group membership affects identity and trust. The 'admin event' framing confirms it is a privileged, potentially irreversible change.
From the tool's definition 'Remove a user from a NIP-29 group' — removal of a user is an irreversible administrative action (kind 9001 admin event) that revokes group membership
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs group-remove-user 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-remove-user, this is the rule to start with:
group-remove-user 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-remove-user call is checked against it from then on.
Questions about group-remove-user
Remove a user from a NIP-29 group (kind 9001 admin event). 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-remove-user: 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-remove-user 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-remove-user 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-remove-user. 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-remove-user 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