AI agents invoke create_live_command to trigger actions in QuantConnect. 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.
This tool sends commands to a live trading algorithm in production. While it doesn't directly move money itself, executing commands on a live trading algorithm can trigger trades, modify positions, or alter trading behavior with real financial consequences. It falls under Execute (triggering external operations) with critical severity due to the potential for significant financial impact from misuse.
From the tool's definition Send a command to a live trading algorithm
Documented attack patterns abuse exactly the kind of access create_live_command gives an agent:
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 create_live_command:
{
"version": "1",
"default": "deny",
"tools": {
"create_live_command": {
"limits": [
{
"counter": "create_live_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Send a command to a live trading algorithm. 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.
Register the QuantConnect MCP server in PolicyLayer and add a rule for create_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.
create_live_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Deterministic rules across all 64 QuantConnect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
64 QuantConnect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.