AI agents call get_brokerage 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. |
witnessAddress | string | Yes | The SR witness address |
Parameters from the server's own tool schema.
This tool retrieves blockchain data (a Super Representative's brokerage ratio) and returns it without creating, modifying, deleting, or executing any operations. It is a pure read operation with no financial impact, no code execution, and no destructive capability. The low severity reflects minimal risk if misused—an agent querying this information poses no direct harm to assets or systems.
From the tool's definition Tool name and description use 'Query' language: 'Query the brokerage ratio'; performs information retrieval only with no side effects or state modification.
Attacks that exploit this kind of access
Query the brokerage ratio (dividend percentage) of a Super Representative. The brokerage value is the percentage that the SR keeps; the rest is distributed to voters. It is categorised as a Read tool in the Tron MCP Server, which means it retrieves data without modifying state.
get_brokerage accepts 2 parameters: network, witnessAddress. Required: witnessAddress. 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 get_brokerage: 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.
get_brokerage 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 get_brokerage 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 get_brokerage. 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.
get_brokerage 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 →