AI agents call list_nodes to retrieve information from Tron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
network | string | — | Network name. Defaults to mainnet. |
Parameters from the server's own tool schema.
This tool retrieves and returns information about TRON network nodes. It performs a query with no side effects—no data is created, modified, deleted, or executed. The returned node addresses are informational metadata about network infrastructure. The blast radius is minimal; misuse would only expose publicly available network topology information. Classified as Read with low severity.
From the tool's definition Tool name 'list_nodes' and description 'List all connected node addresses on the TRON network. Returns an array of node IP:port strings' indicate a read-only query operation that retrieves network topology information without modification or side effects.
Attacks that exploit this kind of access
List all connected node addresses on the TRON network. Returns an array of node IP:port strings. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
list_nodes accepts 1 parameter: network. The full parameter table on this page comes from the server's own tool schema.
Register the Tron MCP server in PolicyLayer and add a rule for list_nodes: 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 Tron. Nothing to install.
list_nodes 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 list_nodes 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 list_nodes. 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.
list_nodes is provided by the Tron MCP server (@bankofai/mcp-server-tron). 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 →