Low Risk

read_backtest_chart

Read a chart from a backtest.

How to control read_backtest_chart ↓

AI agents call read_backtest_chart 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.

Low Risk

This tool retrieves chart data from a completed backtest, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only access existing backtest visualization data it may not be authorized to see, but cannot alter backtests or perform any destructive or financial actions.

From the tool's definition Tool name 'read_backtest_chart' and description 'Read a chart from a backtest' explicitly indicate retrieval of data without modification. The verb 'read' and noun 'chart' denote querying existing backtest results.

Documented attack patterns abuse exactly the kind of access read_backtest_chart 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_backtest_chart:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_backtest_chart": {}
  }
}

read_backtest_chart is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register QuantConnect — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the read_backtest_chart tool do? +

Read a chart from a backtest. It is categorised as a Read tool in the QuantConnect MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_backtest_chart? +

Register the QuantConnect 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. Nothing to install.

What risk level is read_backtest_chart? +

read_backtest_chart is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_backtest_chart? +

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.

How do I block read_backtest_chart completely? +

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.

What MCP server provides read_backtest_chart? +

read_backtest_chart 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.

Enforce policy on every QuantConnect tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.