set_private_key · MERX - TRON Resource Exchange MCP

WHAT IT DOES

What set_private_key does on MERX - TRON Resource Exchange

AI agents use set_private_key to create or update resources in MERX - TRON Resource Exchange — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MERX - TRON Resource Exchange environment.

WHY IT NEEDS A POLICY

Why set_private_key needs a policy

An AI agent can call set_private_key faster than any human can review — one bad instruction and it creates or modifies resources in MERX - TRON Resource Exchange by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_private_key Rate-limited

set_private_key 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": {
    "set_private_key": {
      "limits": [
        {
          "counter": "set_private_key_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 MERX - TRON Resource Exchange, so you can run agents against it safely.

FAQ

Questions about set_private_key

What does the set_private_key tool do? +

Set your TRON private key for this session. Address is derived automatically. Enables write tools: transfer_trx, transfer_trc20, approve_trc20, execute_swap, deposit_trx. Key stays local - never sent to Merx servers. It is categorised as a Write tool in the MERX - TRON Resource Exchange MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_private_key? +

Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for set_private_key: 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 MERX - TRON Resource Exchange. Nothing to install.

What risk level is set_private_key? +

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

Can I rate-limit set_private_key? +

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

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

set_private_key is provided by the MERX - TRON Resource Exchange MCP server (Hovsteder/merx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.