neuron_wallet_transactions
Retrieve the wallet transaction history for the organization, with optional filtering by transaction type.
This record as markdown: /tools/io-github-conquext-neuron/neuron-wallet-transactions.md
What neuron_wallet_transactions does on Neuron
AI agents call neuron_wallet_transactions to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number for pagination (default: 1) |
type | string | — | Filter by transaction type: 'credit' or 'debit' |
limit | integer | — | Number of transactions per page (default: 20) |
Parameters from the server's own tool schema.
Why neuron_wallet_transactions is rated Low
This tool retrieves historical transaction data for viewing/auditing purposes. The verb 'Retrieve' and the function of accessing transaction history are characteristic of Read operations. While it involves financial data, it performs no financial transactions itself (no Financial category applies) and presents no destructive or executable side effects.
From the tool's definition Tool name 'neuron_wallet_transactions' and description 'Retrieve the wallet transaction history' indicate a read operation that queries transaction data without modifying or executing actions.
Attacks that exploit this kind of access
The rule that runs neuron_wallet_transactions 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_wallet_transactions, this is the rule to start with:
neuron_wallet_transactions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_wallet_transactions call is checked against it from then on.
Questions about neuron_wallet_transactions
Retrieve the wallet transaction history for the organization, with optional filtering by transaction type. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_wallet_transactions accepts 3 parameters: page, type, limit. 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_wallet_transactions: 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_wallet_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_wallet_transactions 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_wallet_transactions. 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_wallet_transactions 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.
This server
Across the catalogue