btse_set_leverage · Btse MCP: Risk & Policy

WHAT IT DOES

What btse_set_leverage does on Btse

AI agents invoke btse_set_leverage to trigger actions in Btse. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why btse_set_leverage needs a policy

Setting leverage changes the risk profile of trading positions. While it doesn't directly move money, it alters the multiplier on financial exposure and can lead to liquidations or amplified losses. It's an account configuration change that triggers external state changes on the BTSE Futures platform.

From the tool's definition 'Set leverage for a market. Use leverage=0 for maximum cross leverage.' — modifies trading account leverage settings, which directly affects risk exposure on futures positions

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

btse_set_leverage Rate-limited

btse_set_leverage stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "btse_set_leverage": {
      "limits": [
        {
          "counter": "btse_set_leverage_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about btse_set_leverage

What does the btse_set_leverage tool do? +

Set leverage for a market. Use leverage=0 for maximum cross leverage. It is categorised as a Execute tool in the Btse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on btse_set_leverage? +

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

What risk level is btse_set_leverage? +

btse_set_leverage is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit btse_set_leverage? +

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

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

btse_set_leverage is provided by the Btse MCP server (xbotlive/btse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.