enable_auto_deposit

Configure automatic top-up when balance drops below a threshold. The configuration lives ONLY in the current MCP session — it is held in memory by the MCP server process and is lost on server restart, MCP client reconnect, or server redeploy. Top-ups are signed locally with TRON_PRIVATE_KEY and s...

Server MERX - TRON Resource Exchange Hovsteder/merx-mcp
Category Financial
Risk class Critical
Parameters 00 required

What enable_auto_deposit does on MERX - TRON Resource Exchange

AI agents use enable_auto_deposit to commit financial operations through MERX - TRON Resource Exchange — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why enable_auto_deposit needs a policy

This tool commits financial obligations by automatically triggering deposits/top-ups when balance thresholds are reached. Even though the configuration is session-based and ephemeral, the actual financial transfers are real and irreversible. An agent misconfigured to set very low thresholds or without proper safeguards could drain funds repeatedly.

From the tool's definition Tool configures automatic top-up when balance drops below a threshold, with top-ups signed using TRON_PRIVATE_KEY and sent to deposit address. This moves money (TRON resources) automatically based on configured triggers.

Questions about enable_auto_deposit

What does the enable_auto_deposit tool do? +

Configure automatic top-up when balance drops below a threshold. The configuration lives ONLY in the current MCP session — it is held in memory by the MCP server process and is lost on server restart, MCP client reconnect, or server redeploy. Top-ups are signed locally with TRON_PRIVATE_KEY and sent to your Merx deposit address (memo-routed). For persistent auto-deposit you currently need to call this tool again at the start of each session. It is categorised as a Financial tool in the MERX - TRON Resource Exchange MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on enable_auto_deposit? +

Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for enable_auto_deposit: 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 enable_auto_deposit? +

enable_auto_deposit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit enable_auto_deposit? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.