List members of the authenticated Brighty business. Returns each member as { contact, customer, legalData, membership: { memberId, role, state } } where role is one of MEMBER | VIEWER | PAYER | ADMIN | OWNER. The only filter the API accepts is
AI agents call brighty_list_members to retrieve information from Brighty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries member information from a banking infrastructure server. While it is fundamentally a Read operation (no side effects, no data modification), the context that it queries financial/business membership data on a banking platform elevates the severity from low to medium due to potential exposure of sensitive business and personal information (contact details, legal data, role assignments).
From the tool's definition Tool name is 'brighty_list_members' and description states 'List members of the authenticated Brighty business. Returns each member as { contact, customer, legalData, membership: { memberId, role, state } }'.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List members of the authenticated Brighty business. Returns each member as { contact, customer, legalData, membership: { memberId, role, state } } where role is one of MEMBER | VIEWER | PAYER | ADMIN | OWNER. The only filter the API accepts is. It is categorised as a Read tool in the Brighty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_list_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_list_members is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the brighty_list_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_list_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_list_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 →