AI agents call read_live_logs to retrieve information from QuantConnect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic/operational logs from a running algorithm without modifying state, triggering new actions, or affecting the algorithm's execution. It is purely informational, making it a Read category tool.
From the tool's definition Tool name: 'read_live_logs' with description 'Get the logs of a live algorithm.' The verb 'Get' and the singular action of retrieving logs indicates a read-only operation with no modification or execution of code.
Documented attack patterns abuse exactly the kind of access read_live_logs 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 read_live_logs:
{
"version": "1",
"default": "deny",
"tools": {
"read_live_logs": {}
}
}read_live_logs 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.
Get the logs of a live algorithm. It is categorised as a Read tool in the QuantConnect MCP Server, which means it retrieves data without modifying state.
Register the QuantConnect MCP server in PolicyLayer and add a rule for read_live_logs: 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.
read_live_logs 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_logs 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_logs. 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_logs 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.