Create 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 commit with brighty_start_payout. Returns the created payout including its id.
AI agents use brighty_create_payout to commit financial operations through Brighty MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a payout workflow that is designed to move money via transfers. Although it creates a DRAFT container (not yet committing funds), it is a direct precursor to financial transactions (SEPA/SWIFT payments, mass payouts) and is part of the financial pipeline described in the server description.
From the tool's definition Create a new Brighty payout in DRAFT state... add transfers to it with brighty_create_internal_transfer / brighty_create_external_transfer, then commit with brighty_start_payout
Attacks that exploit this kind of access
Create 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 commit with brighty_start_payout. Returns the created payout including its id. It is categorised as a Financial tool in the Brighty MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_create_payout: 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_create_payout is a Financial 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_create_payout 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_create_payout. 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_create_payout 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 →