neuron_verify_wallet_funding
Verify a wallet funding transaction using the Paystack payment reference to confirm the payment was successful.
This record as markdown: /tools/io-github-conquext-neuron/neuron-verify-wallet-funding.md
What neuron_verify_wallet_funding does on Neuron
AI agents use neuron_verify_wallet_funding 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 |
|---|---|---|---|
reference | string | Yes | Paystack payment reference returned from the checkout session |
Parameters from the server's own tool schema.
Why neuron_verify_wallet_funding is rated Critical
This tool interacts with financial payment infrastructure (Paystack) to verify wallet funding transactions. While 'verify' sounds like a read operation, confirming payment success in a financial system can trigger downstream financial state changes (e.g., crediting a wallet), making it a Financial category tool. Misuse could lead to fraudulent wallet credits or financial system manipulation.
From the tool's definition Verify a wallet funding transaction using the Paystack payment reference to confirm the payment was successful
Attacks that exploit this kind of access
The rule that runs neuron_verify_wallet_funding 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_wallet_funding, this is the rule to start with:
Any call to neuron_verify_wallet_funding 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_wallet_funding call is checked against it from then on.
Questions about neuron_verify_wallet_funding
Verify a wallet funding transaction using the Paystack payment reference to confirm the payment was successful. 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_wallet_funding accepts 1 parameter: reference. Required: reference. 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_wallet_funding: 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_wallet_funding 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_wallet_funding 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_wallet_funding. 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_wallet_funding 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