// SCAN REPORT

Btse

27 tools. 7 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

7 can modify or destroy data

20 read-only

27 tools total

Community server · catalogue entry verified 03/07/2026

How to control Btse ↓

TOOL MAP

What Btse exposes to your agents

Read (20) Write / Execute (2) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Btse tools

Financial · Critical btse_transfer This tool moves money between accounts/wallets, which constitutes a financial transaction that commits resources and creates financial obligations. Financial · Critical btse_close_position Closing a trading position on a futures exchange directly commits or settles a financial obligation, realizing gains or losses. Financial · Critical btse_create_order This tool directly executes financial trades on the BTSE futures market, committing real financial obligations. Financial · Critical btse_safe_market_order This tool places a live market order on a futures exchange (BTSE), directly committing financial obligations.

7 of Btse's 27 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Btse

PolicyLayer is an MCP gateway — it sits between your AI agents and Btse, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "btse_close_position": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "btse_cancel_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "btse_set_risk_limit": {
    "limits": [
      {
        "counter": "btse_set_risk_limit_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "btse_account_overview": {
    "limits": [
      {
        "counter": "btse_account_overview_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Btse — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BTSE →

Instant setup, no code required.

FULL CATALOGUE

All 27 Btse tools

FINANCIAL 4 tools

Financial btse_close_position Close an open position at market price or a specified limit price. Financial btse_create_order Place a futures order. Supports LIMIT, MARKET, and OCO types. Financial btse_safe_market_order Place a MARKET order with a slippage safety check. Financial btse_transfer Transfer funds between BTSE wallets (e.g. spot to futures, or between isolated margin wallets).

DESTRUCTIVE 1 tools

Destructive btse_cancel_order Cancel a specific order by order_id or cl_order_id.

EXECUTE 1 tools

Execute btse_set_leverage Set leverage for a market. Use leverage=0 for maximum cross leverage.

WRITE 1 tools

Write btse_set_risk_limit Set the risk limit tier for a market.

READ 20 tools

Read btse_account_overview Single-call account overview combining wallet balance, open positions, and open orders. Read btse_amend_order Amend an existing order. Read btse_get_account_fees Get maker and taker fee rates. Read btse_get_funding_history Get historical funding rates for a perpetual market. Read btse_get_leverage Get current leverage and margin mode for a market. Read btse_get_market_summary Get market summary for one or all BTSE futures markets. Read btse_get_ohlcv Get OHLCV (candlestick) data for a market. Read btse_get_open_orders List all open (unmatched) orders, optionally filtered by symbol. Read btse_get_order Get details of a specific order. Requires order_id or cl_order_id. Read btse_get_orderbook Get L2 orderbook snapshot (buy and sell quotes at each price level). Read btse_get_positions Get all open futures positions, or for a specific symbol. Read btse_get_price Get mark price, index price, and last traded price for a symbol. Read btse_get_risk_limit Get the current risk limit tier for a market. Read btse_get_trade_history Get your personal trade fill history. Read btse_get_trades Get recent public trade fills for a market. Read btse_get_wallet_balance Get futures wallet balance. Read btse_get_wallet_history Get wallet transaction history (deposits, withdrawals, PnL). Read btse_list_accounts List all configured BTSE account IDs and their environment (testnet or live). Read btse_market_snapshot Single-call market snapshot combining price, orderbook, and recent funding rates. Read btse_position_risk Compute liquidation price, unrealised PnL, and risk flag for an open position.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Btse

Can an AI agent move money through the Btse MCP server? +

Yes. The Btse server exposes 4 financial tools including btse_close_position, btse_create_order, btse_safe_market_order. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Btse MCP server? +

Yes. The Btse server exposes 1 destructive tools including btse_cancel_order. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Btse? +

The Btse server has 1 write tools including btse_set_risk_limit. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Btse.

How many tools does the Btse MCP server expose? +

27 tools across 4 categories: Destructive, Financial, Read, Write. 20 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Btse? +

Register the Btse MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Btse tool call.

Deterministic rules across all 27 Btse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BTSE →

Instant setup, no code required.

27 Btse tools catalogued and risk-classified — across an index of 43,000+ MCP servers.