create_backtest

THE RISK

High Risk

On a quantitative trading platform, 'create_backtest' most likely runs a trading strategy simulation against historical data, which is an execution of computation/external operations. While backtests themselves don't move real money, they consume computational resources and may trigger downstream actions in a trading pipeline.

From the tool's definition Tool name 'create_backtest' on a trading platform MCP server; description is empty and uninformative.

Documented attack patterns abuse exactly the kind of access create_backtest gives an agent:

HOW TO CONTROL CREATE_BACKTEST

PolicyLayer is an MCP gateway — it sits between your AI agents and QuantConnect MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_backtest:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_backtest": {
      "limits": [
        {
          "counter": "create_backtest_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

Create a free account and register QuantConnect MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More QuantConnect MCP Server tools

Financial create_live_algorithm create_live_algorithm Destructive clear_quantconnect_auth Clear current QuantConnect authentication configuration. Returns: Dic Destructive delete_backtest Delete a backtest from a project. Args: project_id: ID of the project Destructive delete_file Delete a file from a QuantConnect project. Args: project_id: ID of th Destructive delete_optimization Delete an optimization. Args: optimization_id: ID of the optimization Destructive delete_project Delete a project from QuantConnect. Args: project_id: The ID of the p Destructive delete_project_collaborator Remove a collaborator from a project. Args: project_id: ID of the pro Execute compile_project Compile a project in QuantConnect. Args: project_id: The ID of the pr

All 50 QuantConnect MCP Server tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in QuantConnect MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the create_backtest tool do? +

create_backtest. 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 (taylorwilsdon/quantconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every QuantConnect MCP Server tool call.

Deterministic rules across all 50 QuantConnect MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN QUANTCONNECT →

Free to start. No card required.

50 QuantConnect MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT CREATE_BACKTEST ON QUANTCONNECT MCP SERVER DOES

// THE RISK

// HOW TO CONTROL CREATE_BACKTEST

// EXPLORE