get_transactions
Get the agent transaction history. Returns both incoming and outgoing payments.
This record as markdown: /tools/io-github-lightningfaucet-lightning-wallet-mcp/get-transactions.md
What get_transactions does on Lightning Wallet
AI agents call get_transactions to retrieve information from Lightning Wallet without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_transactions is rated Low
The tool queries and returns historical transaction data without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects on the wallet or network state. The blast radius of misuse is limited to potential information disclosure about transaction history.
From the tool's definition Tool name is 'get_transactions' and description states it 'Get the agent transaction history' and 'Returns both incoming and outgoing payments.' This is a retrieval operation with no state modification.
Attacks that exploit this kind of access
The rule that runs get_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Lightning Wallet, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_transactions, this is the rule to start with:
get_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 Lightning Wallet, apply this rule, and every get_transactions call is checked against it from then on.
Questions about get_transactions
Get the agent transaction history. Returns both incoming and outgoing payments. It is categorised as a Read tool in the Lightning Wallet MCP Server, which means it retrieves data without modifying state.
Register the Lightning Wallet MCP server in PolicyLayer and add a rule for get_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 Lightning Wallet. Nothing to install.
get_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 get_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 get_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.
get_transactions is provided by the Lightning Wallet MCP server (lightning-wallet-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Lightning Wallet, and thousands of servers like it.
This server
Across the catalogue