Send RGB assets to recipients
AI agents use rgb_send_assets to commit financial operations through RGB Lightning Network MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Sending RGB assets constitutes a financial transfer of digital assets. This action is irreversible once broadcast to the Bitcoin network, and misuse could result in permanent loss of assets. It qualifies as Financial due to committing asset transfers, which is the most severe applicable category.
From the tool's definition 'Send RGB assets to recipients' — transfers RGB assets (digital assets on Bitcoin/Lightning Network) to external parties
Attacks that exploit this kind of access
Send RGB assets to recipients. It is categorised as a Financial tool in the RGB Lightning Network MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the RGB Lightning Network MCP Server MCP server in PolicyLayer and add a rule for rgb_send_assets: 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_send_assets 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 rgb_send_assets 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_send_assets. 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_send_assets 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 →