Low Risk

read_project_nodes

Read the available and selected nodes of a project. Args: project_id: ID of the project to read nodes for Returns: Dictionary containing project node information

How to control read_project_nodes ↓

AI agents call read_project_nodes 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

This tool performs a read-only retrieval operation. It takes a project_id as input and returns project node information without creating, modifying, deleting, or executing any operations. The explicit use of 'Read' in the description and the passive retrieval nature of the operation clearly place this in the Read category. Severity is low as it merely queries existing data with no blast radius from misuse.

From the tool's definition Tool name 'read_project_nodes' and description 'Read the available and selected nodes of a project' with Returns indicating it retrieves and queries project node information without modification or side effects.

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

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

read_project_nodes 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_project_nodes tool do? +

Read the available and selected nodes of a project. Args: project_id: ID of the project to read nodes for Returns: Dictionary containing project node information. 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_project_nodes? +

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

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

Can I rate-limit read_project_nodes? +

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

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

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