quick_backtest · Ai Trader MCP: Risk & Policy

WHAT IT DOES

What quick_backtest does on Ai Trader

AI agents invoke quick_backtest to trigger actions in Ai Trader. 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 quick_backtest needs a policy

Based on the server context (ai-trader) and sibling tools (run_backtest, fetch_market_data, list_strategies), this tool almost certainly runs a backtest simulation — executing trading algorithm logic against historical data. While backtests are simulations and not live trades, they involve executing code/algorithms and could potentially trigger unintended financial operations if connected to live systems.

From the tool's definition Tool name 'quick_backtest' on a server described as enabling backtests of trading algorithms; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

quick_backtest Rate-limited

quick_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": {
    "quick_backtest": {
      "limits": [
        {
          "counter": "quick_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 Ai Trader, so you can run agents against it safely.

FAQ

Questions about quick_backtest

What does the quick_backtest tool do? +

quick_backtest. It is categorised as a Execute tool in the Ai Trader MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on quick_backtest? +

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

What risk level is quick_backtest? +

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

Can I rate-limit quick_backtest? +

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

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

quick_backtest is provided by the Ai Trader MCP server (whchien/ai-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.