neuron_verify_bank_account
Verify a Nigerian bank account number via Paystack to confirm the account holder name before saving.
This record as markdown: /tools/io-github-conquext-neuron/neuron-verify-bank-account.md
What neuron_verify_bank_account does on Neuron
AI agents use neuron_verify_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) |
accountNumber | string | Yes | 10-digit Nigerian bank account number to verify |
Parameters from the server's own tool schema.
Why neuron_verify_bank_account is rated Critical
This tool interfaces with Paystack, a financial payment platform, to verify bank account details. While it appears to be a read/verification operation, it involves financial infrastructure (bank accounts, payment processor) and the act of 'saving' verified account details creates financial data records that could enable subsequent payment operations.
From the tool's definition 'Verify a Nigerian bank account number via Paystack to confirm the account holder name before saving'
Attacks that exploit this kind of access
The rule that runs neuron_verify_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_verify_bank_account, this is the rule to start with:
Any call to neuron_verify_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_verify_bank_account call is checked against it from then on.
Questions about neuron_verify_bank_account
Verify a Nigerian bank account number via Paystack to confirm the account holder name before saving. 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_verify_bank_account accepts 2 parameters: bankCode, accountNumber. Required: bankCode, 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_verify_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_verify_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_verify_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_verify_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_verify_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