Low Risk

read_live_chart

read_live_chart

How to control read_live_chart ↓

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

Low Risk

The tool retrieves and displays chart data in real-time without creating, modifying, executing code, or destroying data. While the description is empty, the name strongly suggests a read operation. Given the QuantConnect platform context (backtesting and live trading), this would fetch existing chart/performance data. Confidence is slightly reduced due to missing description, but the naming convention is clear.

From the tool's definition Tool name is 'read_live_chart', where 'read' indicates retrieval of data without modification, and 'live_chart' refers to real-time market or algorithm performance visualization data.

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

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

read_live_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 MCP Server — 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_live_chart tool do? +

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

How do I enforce a policy on read_live_chart? +

Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for read_live_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.

What risk level is read_live_chart? +

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

Can I rate-limit read_live_chart? +

Yes. Add a rate_limit block to the read_live_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_live_chart completely? +

Set action: deny in the PolicyLayer policy for read_live_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_live_chart? +

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

Enforce policy on every QuantConnect MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.