run_backtest

Server Bitbank tjackiet/bitbank-lab-mcp

Category Execute

Risk class High

Parameters 00 required

WHAT IT DOES

What run_backtest does on Bitbank

AI agents invoke run_backtest to trigger actions in Bitbank. 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 run_backtest needs a policy

run_backtest triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_backtest Rate-limited

run_backtest 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": {
    "run_backtest": {
      "limits": [
        {
          "counter": "run_backtest_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 Bitbank, so you can run agents against it safely.

FAQ

Questions about run_backtest

What does the run_backtest tool do? +

[Backtest / Strategy Test / SMA Cross / RSI / MACD] 汎用バックテスト（backtest / strategy test / simulation / performance）。データ取得〜計算〜チャート描画を一括実行。戦略: sma_cross / rsi / macd_cross / bb_breakout。期間: 1M / 3M / 6M / 1Y / 2Y / 3Y、または start_date+end_date (YYYY-MM-DD) で任意レンジ指定可。時間軸: 1D / 4H / 1H。 SVG チャート付きで損益・勝率・最大DD・Sharpe Ratio 等を返却。 content テキスト末尾に equity_curve / drawdown_curve の JSON を含む（chartDetail=default は最大 200 点の均等サンプル、full は全点）。独自実装不要。. It is categorised as a Execute tool in the Bitbank MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_backtest? +

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

What risk level is run_backtest? +

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

Can I rate-limit run_backtest? +

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

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

run_backtest is provided by the Bitbank MCP server (tjackiet/bitbank-lab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.