set_api_key

Set your Merx API key for this session. Unlocks all authenticated tools (trading, balance, orders). Use this if you already have an API key.

Handles credentials or secrets (api_key)

Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

merx-mcp Write Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents use set_api_key to create or modify resources in MERX - TRON Resource Exchange. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON SET_API_KEY

Without a policy, an AI agent could call set_api_key repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach MERX - TRON Resource Exchange.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

merx-tron-resource-exchange.yaml

tools:
  set_api_key:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full MERX - TRON Resource Exchange policy for all 54 tools.

// DETAILS

Tool Name set_api_key

Category Write

MCP Server MERX - TRON Resource Exchange MCP Server

Risk Level Medium

// MORE MERX - TRON RESOURCE EXCHANGE TOOLS

Financial deposit_trx Financial enable_auto_deposit Financial pay_invoice Financial transfer_trc20 Financial transfer_trx Financial withdraw Execute call_contract Execute compile_policy

View all 54 tools →

// RELATED READING

// FAQ

What does the set_api_key tool do? +

Set your Merx API key for this session. Unlocks all authenticated tools (trading, balance, orders). Use this if you already have an API key.. 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_api_key? +

Add a rule in your Intercept YAML policy under the tools section for set_api_key. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MERX - TRON Resource Exchange MCP server.

What risk level is set_api_key? +

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

Can I rate-limit set_api_key? +

Yes. Add a rate_limit block to the set_api_key rule in your Intercept 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_api_key completely? +

Set action: deny in the Intercept policy for set_api_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_api_key? +

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

set_api_key

Enforce policies on MERX - TRON Resource Exchange