brighty_create_external_transfer

Add 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 beneficiary.kind field, or pass a saved

Server Brighty MCP Server razz-team/brighty-agent-toolkit
Category Financial
Risk class Critical
Parameters 00 required

What brighty_create_external_transfer does on Brighty MCP Server

AI agents use brighty_create_external_transfer to commit financial operations through Brighty MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why brighty_create_external_transfer needs a policy

This tool directly initiates financial transfers of money to external recipients (via IBAN, BIC, account numbers, or blockchain addresses). It moves funds outside the Brighty platform, committing financial obligations.

From the tool's definition Tool name contains 'create_external_transfer' and description explicitly states it 'Add an external transfer (off-Brighty) to a payout' with support for fiat payments via IBAN/BIC and crypto transfers.

Questions about brighty_create_external_transfer

What does the brighty_create_external_transfer tool do? +

Add 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 beneficiary.kind field, or pass a saved. 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.

How do I enforce a policy on brighty_create_external_transfer? +

Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_create_external_transfer: 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.

What risk level is brighty_create_external_transfer? +

brighty_create_external_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit brighty_create_external_transfer? +

Yes. Add a rate_limit block to the brighty_create_external_transfer 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.

How do I block brighty_create_external_transfer completely? +

Set action: deny in the PolicyLayer policy for brighty_create_external_transfer. 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.

What MCP server provides brighty_create_external_transfer? +

brighty_create_external_transfer 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.

// THE FULL RECORD

brighty_create_external_transfer is one line of Brighty MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.