Execute an FX transfer between two of the business
AI agents use brighty_transfer_own 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 directly transfers funds (foreign exchange transfers) between business accounts. Any FX transfer commits a financial obligation and moves money, which cannot be easily reversed without additional transactions. The blast radius of misuse is severe: an agent could transfer arbitrary amounts between accounts, causing immediate financial loss. This is the highest severity risk category.
From the tool's definition Tool name 'brighty_transfer_own' and description 'Execute an FX transfer between two of the business' indicate movement of money between accounts.
Attacks that exploit this kind of access
Execute an FX transfer between two of the business. 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_transfer_own: 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_transfer_own 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_transfer_own 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_transfer_own. 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_transfer_own 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 →