Critical-risk tools in Brighty MCP Server
9 of the 23 tools in Brighty MCP Server are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
brighty_remove_membersDestructiveRemove 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.
-
brighty_terminate_accountDestructiveClose a Brighty account. The account must be empty (zero balance) and not the primary account. This is irreversible.
-
brighty_create_external_transferFinancialAdd an external transfer (off-Brighty) to a payout. Discriminates between fiat (IBAN/BIC/account-number) and crypto (on-chain address + network id) recipients via the beneficiar...
-
brighty_create_internal_transferFinancialAdd an internal transfer (Brighty-to-Brighty) to a payout. Recipient is identified by
-
brighty_create_payoutFinancialCreate a new Brighty payout in DRAFT state. The payout is an empty container; add transfers to it with brighty_create_internal_transfer / brighty_create_external_transfer, then ...
-
brighty_order_cardFinancialOrder a new Brighty card. Two-step: first POST /cards/order/intent (returns fees, amount, and a short-lived hash), then POST /cards/order with hash + fees + sourceAccountId and ...
-
brighty_set_card_limitsFinancialReplace a Brighty card
-
brighty_transfer_intentFinancialPreview an FX transfer between two of the business
-
brighty_transfer_ownFinancialExecute an FX transfer between two of the business
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.