AI agents use liquidate_live_algorithm to commit financial operations through QuantConnect — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Liquidating a live algorithm involves closing all open market positions, which constitutes real financial transactions with immediate and potentially irreversible monetary consequences. This is a Financial action with critical severity since misuse could cause significant financial losses by force-closing positions at unfavorable times.
From the tool's definition 'Liquidate and stop a live algorithm' — liquidation of a live trading algorithm implies selling/closing all open financial positions
Documented attack patterns abuse exactly the kind of access liquidate_live_algorithm 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 liquidate_live_algorithm:
{
"version": "1",
"default": "deny",
"tools": {
"liquidate_live_algorithm": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to liquidate_live_algorithm is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Liquidate and stop a live algorithm. It is categorised as a Financial tool in the QuantConnect MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the QuantConnect MCP server in PolicyLayer and add a rule for liquidate_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. Nothing to install.
liquidate_live_algorithm is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the liquidate_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.
Set action: deny in the PolicyLayer policy for liquidate_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.
liquidate_live_algorithm 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.