neuron_save_bank_account
Save a verified bank account as the organization's payout destination. Verify the account first using neuron_verify_bank_account.
This record as markdown: /tools/io-github-conquext-neuron/neuron-save-bank-account.md
What neuron_save_bank_account does on Neuron
AI agents use neuron_save_bank_account to commit financial operations through Neuron, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
bankCode | string | Yes | Nigerian bank code (e.g., '058' for GTBank, '044' for Access Bank) |
bankName | string | Yes | Full name of the bank (e.g., 'Guaranty Trust Bank') |
accountName | string | Yes | Account holder name as returned from bank verification |
accountNumber | string | Yes | 10-digit Nigerian bank account number |
Parameters from the server's own tool schema.
Why neuron_save_bank_account is rated Critical
Setting a payout destination bank account is a financial action that determines where funds are transferred. An attacker or misconfigured AI could redirect an organization's payouts to an unauthorized account, making this critical severity under the Financial category.
From the tool's definition 'Save a verified bank account as the organization's payout destination' — directly configures where financial payouts are sent, which is a financial operation with severe consequences if misused.
Attacks that exploit this kind of access
The rule that runs neuron_save_bank_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_save_bank_account, this is the rule to start with:
Any call to neuron_save_bank_account is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_save_bank_account call is checked against it from then on.
Questions about neuron_save_bank_account
Save a verified bank account as the organization's payout destination. Verify the account first using neuron_verify_bank_account. It is categorised as a Financial tool in the Neuron MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
neuron_save_bank_account accepts 4 parameters: bankCode, bankName, accountName, accountNumber. Required: bankCode, bankName, accountName, accountNumber. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_save_bank_account: 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 Neuron. Nothing to install.
neuron_save_bank_account 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 neuron_save_bank_account 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 neuron_save_bank_account. 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.
neuron_save_bank_account is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
Across the catalogue