broadcast_live_command

THE RISK

High Risk

Broadcasting commands to live algorithms constitutes triggering external operations whose effects depend on arguments. Since these are live (real-money) trading algorithms, misuse could have financial consequences indirectly, but the direct action is executing a command broadcast. The blast radius is high because it affects ALL live algorithms simultaneously, not just one.

From the tool's definition 'Broadcast a live command to all live algorithms' — triggers external operations on running live trading algorithms

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

HOW TO CONTROL BROADCAST_LIVE_COMMAND

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

policy.json

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

broadcast_live_command 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 — 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 tools

Financial liquidate_live_algorithm Liquidate and stop a live algorithm. Destructive delete_backtest Delete a backtest from a project. Destructive delete_file Delete a file in a project. Destructive delete_object Delete the Object Store file of a specific organization and Destructive delete_optimization Delete an optimization. Destructive delete_project Delete a project. Destructive delete_project_collaborator Remove a collaborator from a project. Execute stop_live_algorithm Stop a live algorithm.

All 64 QuantConnect 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 → 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 broadcast_live_command tool do? +

Broadcast a live command to all live algorithms in an. It is categorised as a Execute tool in the QuantConnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on broadcast_live_command? +

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

What risk level is broadcast_live_command? +

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

Can I rate-limit broadcast_live_command? +

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

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

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

Enforce policy on every QuantConnect tool call.

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

GOVERN QUANTCONNECT →

Free to start. No card required.

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

// WHAT BROADCAST_LIVE_COMMAND ON QUANTCONNECT DOES

// THE RISK

// HOW TO CONTROL BROADCAST_LIVE_COMMAND

// EXPLORE