Sign a message with the RGB node
AI agents invoke rgb_sign_message to trigger actions in RGB Lightning Network MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Signing a message is an execution operation that uses the node's private keys to produce a cryptographic signature. It doesn't read data passively, write/modify stored data, or move funds directly, but it does perform an external cryptographic operation. Misuse could lead to signing malicious messages or facilitating fraud, though it doesn't directly move funds or destroy data.
From the tool's definition 'Sign a message with the RGB node' — triggers a cryptographic signing operation on the node using private key material
Attacks that exploit this kind of access
Sign a message with the RGB node. It is categorised as a Execute tool in the RGB Lightning Network MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RGB Lightning Network MCP Server MCP server in PolicyLayer and add a rule for rgb_sign_message: 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_sign_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rgb_sign_message 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_sign_message. 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_sign_message 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 →