update_brokerage · Tron MCP: Risk & Policy

WHAT IT DOES

What update_brokerage does on Tron

AI agents use update_brokerage to create or update resources in Tron — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tron environment.

PARAMETERS

Parameter	Type	Required	Description
`network`	string	—	Network name. Defaults to mainnet.
`brokerage`	integer	Yes	Brokerage percentage kept by the SR (0-100). E.g. 20 means SR keeps 20%.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_brokerage needs a policy

This tool modifies the brokerage ratio for a Super Representative on the TRON blockchain, which directly affects how rewards are distributed between the SR and voters. It is a reversible configuration change (can be updated again), placing it in Write.

From the tool's definition Update the SR brokerage ratio (dividend ratio). Only callable by an SR. Value is the percentage the SR keeps (0-100); the remainder goes to voters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_brokerage Rate-limited

update_brokerage stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_brokerage": {
      "limits": [
        {
          "counter": "update_brokerage_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tron, so you can run agents against it safely.

FAQ

Questions about update_brokerage

What does the update_brokerage tool do? +

Update the SR brokerage ratio (dividend ratio). Only callable by an SR. Value is the percentage the SR keeps (0-100); the remainder goes to voters. It is categorised as a Write tool in the Tron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_brokerage accept? +

update_brokerage accepts 2 parameters: network, brokerage. Required: brokerage. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_brokerage? +

Register the Tron MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_brokerage? +

update_brokerage is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_brokerage? +

Yes. Add a rate_limit block to the update_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.

How do I block update_brokerage completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_brokerage? +

update_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.