List all the backtests for the project.
AI agents call list_backtests 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 queries and returns existing backtest data without modifying, executing, or deleting anything. It is a straightforward read operation that retrieves information from QuantConnect's platform. The severity is low because listing backtests poses minimal risk—it only exposes metadata about past test runs without triggering trades, code execution, or data destruction.
From the tool's definition Tool name 'list_backtests' and description 'List all the backtests for the project' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all the backtests for the project. 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 list_backtests: 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.
list_backtests 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 list_backtests 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 list_backtests. 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.
list_backtests 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 →