List on-chain transactions
AI agents call rgb_list_transactions to retrieve information from RGB Lightning Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays historical transaction data without modifying, executing operations, or affecting blockchain state. It is purely a read operation for information gathering, similar to viewing a transaction history or ledger query. No irreversible actions, code execution, or financial commitments are involved.
From the tool's definition Tool name 'rgb_list_transactions' and description 'List on-chain transactions' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List on-chain transactions. It is categorised as a Read tool in the RGB Lightning Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RGB Lightning Network MCP Server MCP server in PolicyLayer and add a rule for rgb_list_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 RGB Lightning Network MCP Server. Nothing to install.
rgb_list_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 rgb_list_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 rgb_list_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.
rgb_list_transactions is provided by the RGB Lightning Network MCP Server MCP server (lnfi-network/rgb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →