broadcast_hex · Tron MCP: Risk & Policy

WHAT IT DOES

What broadcast_hex does on Tron

AI agents invoke broadcast_hex to trigger actions in Tron. 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.

PARAMETERS

Parameter	Type	Required	Description
`network`	string	—	Network name. Defaults to mainnet.
`transaction`	string	Yes	Signed transaction hex string

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why broadcast_hex needs a policy

This tool submits a pre-signed transaction to the TRON blockchain network, triggering irreversible on-chain execution. While it does not itself create or sign the transaction, broadcasting it causes real, permanent blockchain effects (transfers, contract calls, etc.) that cannot be undone.

From the tool's definition Broadcast a signed, protocol buffer-encoded transaction hex string to the TRON network

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

broadcast_hex Rate-limited

broadcast_hex stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "broadcast_hex": {
      "limits": [
        {
          "counter": "broadcast_hex_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 broadcast_hex

What does the broadcast_hex tool do? +

Broadcast a signed, protocol buffer-encoded transaction hex string to the TRON network. It is categorised as a Execute tool in the Tron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does broadcast_hex accept? +

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

How do I enforce a policy on broadcast_hex? +

Register the Tron MCP server in PolicyLayer and add a rule for broadcast_hex: 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 broadcast_hex? +

broadcast_hex is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit broadcast_hex? +

Yes. Add a rate_limit block to the broadcast_hex 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 broadcast_hex completely? +

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

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