update_backtest · QuantConnect MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_backtest does on QuantConnect MCP Server

AI agents use update_backtest to create or update resources in QuantConnect MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuantConnect MCP Server environment.

WHY IT NEEDS A POLICY

Why update_backtest needs a policy

The tool updates backtest properties (name and note fields), which are reversible metadata changes. This is clearly a Write operation—it creates or modifies data without deleting, executing code, or triggering trading actions. While the parent server handles financial/trading operations, this specific tool only modifies backtest documentation.

From the tool's definition Tool performs 'update' operation on backtest metadata (name or note), which modifies data reversibly without destructive effects or side effects on trading systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_backtest Rate-limited

update_backtest stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_backtest": {
      "limits": [
        {
          "counter": "update_backtest_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_backtest

What does the update_backtest tool do? +

Update the name or note of a backtest. It is categorised as a Write tool in the QuantConnect MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_backtest? +

Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for update_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 update_backtest? +

update_backtest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_backtest? +

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

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

update_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.