run_backtest

Run a backtest on historical data for a trading strategy via the GT backtest service.

SERVER:GT Protocol MCP Server SOURCEgt-protocol/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gt-protocol-mcp/run-backtest.md

WHAT IT DOES

What run_backtest does on :GT Protocol MCP Server

AI agents invoke run_backtest to trigger actions in :GT Protocol MCP Server. 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.

RISK

Why run_backtest is rated High

While backtesting operates on historical data rather than live markets, it is fundamentally an Execute operation: it runs strategy code through the GT backtest service. The severity is high because misconfigured or malicious strategies could consume excessive resources, reveal sensitive trading logic, or be used to probe exchange APIs.

From the tool's definition The tool 'run_backtest' executes a trading strategy against historical data via the GT backtest service. The description indicates it 'runs' a backtest, which involves executing code/logic.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_backtest safely

PolicyLayer is an MCP gateway: it sits between your AI agents and :GT Protocol MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_backtest, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect :GT Protocol MCP Server, apply this rule, and every run_backtest call is checked against it from then on.

FAQ

Questions about run_backtest

What does the run_backtest tool do? +

Run a backtest on historical data for a trading strategy via the GT backtest service. It is categorised as a Execute tool in the :GT Protocol MCP Server 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 :GT Protocol MCP Server 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 :GT Protocol MCP Server. 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 :GT Protocol MCP Server MCP server (gt-protocol/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on :GT Protocol MCP Server, and thousands of servers like it.

This server

All 19 :GT Protocol MCP Server tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →