Get RGB node information including ID, version, and network status
AI agents call rgb_get_node_info 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 informational data about the RGB node (ID, version, network status) with no side effects, state changes, or operations triggered. It is purely observational and returns static or status information. No asset movements, transactions, or code execution are involved.
From the tool's definition Tool name 'rgb_get_node_info' and description 'Get RGB node information including ID, version, and network status' indicate a read-only retrieval operation that queries node metadata without modifying or executing operations.
Attacks that exploit this kind of access
Get RGB node information including ID, version, and network status. 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_get_node_info: 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_get_node_info 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_get_node_info 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_get_node_info. 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_get_node_info 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 →