Invite one or more teammates to the authenticated Brighty business. Each entry needs email and role; legalName / birthInfo / nationality are optional KYC pre-fills. Returns an array of Membership { memberId, role, state }.
AI agents use brighty_add_members to create or update resources in Brighty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brighty MCP Server environment.
This tool creates new user accounts/memberships within a banking infrastructure platform, which modifies the platform's user roster and access permissions. While it does not move money (Financial) or delete data (Destructive), it irreversibly adds new members with roles that grant privileges. This is a Write operation because it creates data (memberships) with reversible effects (members can be removed).
From the tool's definition Tool description explicitly states it 'Invite[s] one or more teammates to the authenticated Brighty business' and 'Returns an array of Membership', indicating it creates new user memberships and modifies access controls to a financial platform.
Attacks that exploit this kind of access
Invite one or more teammates to the authenticated Brighty business. Each entry needs email and role; legalName / birthInfo / nationality are optional KYC pre-fills. Returns an array of Membership { memberId, role, state }. It is categorised as a Write tool in the Brighty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_add_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_add_members is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the brighty_add_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_add_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_add_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 →