change_leverage · Bitunix MCP: Risk & Policy

WHAT IT DOES

What change_leverage does on Bitunix MCP

AI agents use change_leverage to commit financial operations through Bitunix MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why change_leverage needs a policy

Changing leverage on futures positions directly affects financial exposure and risk. Increasing leverage amplifies potential gains and losses on open positions, which constitutes committing or modifying financial obligations. Misuse could lead to liquidation of positions or dramatically increased financial risk.

From the tool's definition Change the leverage for a futures symbol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_leverage Approval-gated

Any call to change_leverage is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "change_leverage": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bitunix MCP, so you can run agents against it safely.

FAQ

Questions about change_leverage

What does the change_leverage tool do? +

Change the leverage for a futures symbol. It is categorised as a Financial tool in the Bitunix MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on change_leverage? +

Register the Bitunix MCP server in PolicyLayer and add a rule for change_leverage: 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 Bitunix MCP. Nothing to install.

What risk level is change_leverage? +

change_leverage 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 change_leverage? +

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

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

change_leverage is provided by the Bitunix MCP server (luiinventions/bitunix-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.