Read comprehensive live algorithm statistics, runtime data, and details. Args: project_id: ID of the project with the live algorithm deploy_id: Optional deploy ID for specific algorithm (omit to get latest) Returns: Dictionary containing detailed live algorithm statistics, runtime data, charts, a...
AI agents call read_live_algorithm to retrieve information from QuantConnect MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about live trading algorithms without creating, modifying, deleting, or executing any actions. However, the severity is elevated to 'medium' rather than 'low' because the retrieved data includes live trading statistics and runtime information from an active financial trading system, which could be sensitive or reveal proprietary trading strategies if disclosed to unauthorized…
From the tool's definition Tool name is 'read_live_algorithm' and description states it 'Read[s] comprehensive live algorithm statistics, runtime data, and details' with no modification or deletion capabilities mentioned.
Documented attack patterns abuse exactly the kind of access read_live_algorithm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuantConnect MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_live_algorithm:
{
"version": "1",
"default": "deny",
"tools": {
"read_live_algorithm": {}
}
}read_live_algorithm is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read comprehensive live algorithm statistics, runtime data, and details. Args: project_id: ID of the project with the live algorithm deploy_id: Optional deploy ID for specific algorithm (omit to get latest) Returns: Dictionary containing detailed live algorithm statistics, runtime data, charts, and files. It is categorised as a Read tool in the QuantConnect MCP Server MCP Server, which means it retrieves data without modifying state.
Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for read_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.
read_live_algorithm is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_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 read_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.
read_live_algorithm is provided by the QuantConnect MCP Server MCP server (taylorwilsdon/quantconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 QuantConnect MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 QuantConnect MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.