Read a chart from a backtest.
AI agents call read_backtest_chart 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 displays backtest chart data without creating, modifying, deleting, or executing code. It is a pure data query operation with no consequential side effects, fitting squarely within the Read category. The low severity reflects minimal risk even if misused by an AI agent—viewing backtest results poses no financial, operational, or data integrity threat.
From the tool's definition Tool name is 'read_backtest_chart' with verb 'read'; description states 'Read a chart from a backtest' indicating data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Read a chart from a backtest. 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_chart: 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_chart 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_chart 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_chart. 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_chart is provided by the QuantConnect MCP Server MCP server (mymanish9-code11/quantconnect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →