brighty_create_internal_transfer

Add an internal transfer (Brighty-to-Brighty) to a payout. Recipient is identified by

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

What brighty_create_internal_transfer does on Brighty MCP Server

AI agents use brighty_create_internal_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_internal_transfer needs a policy

This tool moves money between accounts within the Brighty banking platform. Financial tools that commit monetary transactions carry the highest severity due to irreversible consequences: funds transferred cannot be recovered without explicit reversal by authorized parties. An AI agent with access could drain accounts, perform unauthorized transfers, or cause financial harm.

From the tool's definition Tool name 'brighty_create_internal_transfer' combined with server description stating 'send SEPA/SWIFT payments, run mass payouts' and sibling tool 'brighty_create_payout' indicates this transfers money between Brighty accounts.

Questions about brighty_create_internal_transfer

What does the brighty_create_internal_transfer tool do? +

Add an internal transfer (Brighty-to-Brighty) to a payout. Recipient is identified by. 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_internal_transfer? +

Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_create_internal_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_internal_transfer? +

brighty_create_internal_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_internal_transfer? +

Yes. Add a rate_limit block to the brighty_create_internal_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_internal_transfer completely? +

Set action: deny in the PolicyLayer policy for brighty_create_internal_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_internal_transfer? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.