stop_live_algorithm · QuantConnect MCP Server MCP

WHAT IT DOES

What stop_live_algorithm does on QuantConnect MCP Server

AI agents invoke stop_live_algorithm 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 stop_live_algorithm needs a policy

This tool executes an action that stops a live trading algorithm, which is an irreversible operational state change with real-time market implications. It is Execute (not Destructive) because it does not permanently delete or purge data—the algorithm can be restarted. It is high severity because misuse could halt profitable live trading, cause missed market opportunities, or leave positions unsecured.

From the tool's definition The tool description indicates it 'Stop[s] a live algorithm' - this triggers an external operation that halts an active algorithmic trading process.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_live_algorithm Rate-limited

stop_live_algorithm 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": {
    "stop_live_algorithm": {
      "limits": [
        {
          "counter": "stop_live_algorithm_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 stop_live_algorithm

What does the stop_live_algorithm tool do? +

Stop a live algorithm. 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 stop_live_algorithm? +

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

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

Can I rate-limit stop_live_algorithm? +

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

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

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