Low Risk

read_lean_versions

Returns a list of LEAN versions with basic information for

How to control read_lean_versions ↓

AI agents call read_lean_versions 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 queries and retrieves LEAN framework version information. It performs a read-only operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only retrieve version metadata, which poses no security risk.

From the tool's definition Tool name 'read_lean_versions' and description 'Returns a list of LEAN versions with basic information' indicate retrieval of version data without modification or side effects.

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

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

read_lean_versions 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_lean_versions tool do? +

Returns a list of LEAN versions with basic information for. 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_lean_versions? +

Register the QuantConnect MCP server in PolicyLayer and add a rule for read_lean_versions: 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_lean_versions? +

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

Can I rate-limit read_lean_versions? +

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

Set action: deny in the PolicyLayer policy for read_lean_versions. 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_lean_versions? +

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