create_backtest · QuantConnect MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_backtest does on QuantConnect MCP Server

AI agents invoke create_backtest to trigger actions in QuantConnect 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.

WHY IT NEEDS A POLICY

Why create_backtest needs a policy

Creating a backtest triggers execution of a trading algorithm simulation on QuantConnect's platform. This is an Execute action — it runs a computational process (strategy simulation) with effects that depend on the algorithm and parameters provided. While not directly destructive or financial, it consumes compute resources and initiates a backend job.

From the tool's definition Create a new backtest request and get the backtest Id

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_backtest Rate-limited

create_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": {
    "create_backtest": {
      "limits": [
        {
          "counter": "create_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 QuantConnect MCP Server, so you can run agents against it safely.

FAQ

Questions about create_backtest

What does the create_backtest tool do? +

Create a new backtest request and get the backtest Id. It is categorised as a Execute tool in the QuantConnect 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 create_backtest? +

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

What risk level is create_backtest? +

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

Can I rate-limit create_backtest? +

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

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

create_backtest is provided by the QuantConnect MCP Server MCP server (mymanish9-code11/quantconnect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.