Remove one or more members from the authenticated Brighty business. The acting key must have an admin-grade role. This is irreversible; removed members can be re-invited later.
AI agents call brighty_remove_members to permanently remove resources in Brighty MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing members from an authenticated business account is an irreversible action that permanently severs access and potentially affects operational continuity, compliance, and financial controls. While the description clarifies members can be re-invited, the immediate removal itself cannot be undone and represents a destructive modification to the business structure.
From the tool's definition Tool description states 'Remove one or more members' and explicitly notes 'This is irreversible'; combined with server context (Banking infrastructure for AI agents) and admin-level access requirement ('acting key must have an admin-grade role').
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Remove one or more members from the authenticated Brighty business. The acting key must have an admin-grade role. This is irreversible; removed members can be re-invited later. It is categorised as a Destructive tool in the Brighty MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_remove_members: 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 Brighty MCP Server. Nothing to install.
brighty_remove_members 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 brighty_remove_members 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 brighty_remove_members. 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.
brighty_remove_members is provided by the Brighty MCP Server MCP server (razz-team/brighty-agent-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →