Register your TRON address as an agent on agent.merx.exchange. Required ONCE before using request_payment, create_invoice, watch_address, agent_status, or any other agent payment tool. Pass the TRON address you want to use as the on-chain identity for this API key. Idempotent — calling twice with...
AI agents use register_agent 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.
This tool creates a new agent registration record on the TRON resource exchange, which is a reversible write operation. While it is a prerequisite for payment and financial tools, the registration action itself doesn't move money or create financial obligations—it just sets up the identity needed for those later operations.
From the tool's definition The tool description states it will 'Register your TRON address as an agent on agent.merx.exchange' and is 'Required ONCE before using request_payment, create_invoice, watch_address, agent_status, or any other agent payment tool.' The verb 'Register' and the…
Attacks that exploit this kind of access
Register your TRON address as an agent on agent.merx.exchange. Required ONCE before using request_payment, create_invoice, watch_address, agent_status, or any other agent payment tool. Pass the TRON address you want to use as the on-chain identity for this API key. Idempotent — calling twice with the same key returns the existing registration. Auth required (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.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for register_agent: 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.
register_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_agent 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 register_agent. 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.
register_agent 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.
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 →