Read insights from a backtest. Args: project_id: ID of the project containing the backtest backtest_id: ID of the backtest to read insights from start: Starting index of insights to fetch (default: 0) end: Last index of insights to fetch (default: 100, max range: 100) Returns: Dictionary containi...
AI agents call read_backtest_insights 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 backtest insights data using pagination parameters. It performs a query operation that returns information without creating, modifying, deleting, or executing any code. The lack of any state-changing operations and explicit 'read' terminology clearly indicates a Read category classification.
From the tool's definition Tool name contains 'read' and description states 'Read insights from a backtest' with parameters for fetching data (project_id, backtest_id, start, end indices) that return insights data without modification or side effects.
Documented attack patterns abuse exactly the kind of access read_backtest_insights 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_backtest_insights:
{
"version": "1",
"default": "deny",
"tools": {
"read_backtest_insights": {}
}
}read_backtest_insights 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 insights from a backtest. Args: project_id: ID of the project containing the backtest backtest_id: ID of the backtest to read insights from start: Starting index of insights to fetch (default: 0) end: Last index of insights to fetch (default: 100, max range: 100) Returns: Dictionary containing insights data and total count. 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_backtest_insights: 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_backtest_insights 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_backtest_insights 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_backtest_insights. 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_backtest_insights 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.