Critical Risk →

delete_project

Delete a project from QuantConnect. Args: project_id: The ID of the project to delete. Returns: A dictionary containing the deletion result.

How to control delete_project ↓

AI agents call delete_project to permanently remove resources in QuantConnect MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool permanently removes a project and its associated data from QuantConnect. Deletion is irreversible and represents a destructive action that cannot be undone. While the blast radius is somewhat contained to a single project rather than system-wide, an AI agent misusing this tool could destroy significant trading research, strategy implementations, or backtest data.

From the tool's definition Tool name is 'delete_project' with description 'Delete a project from QuantConnect.' The verb 'delete' combined with the action of removing a project indicates irreversible data destruction.

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_project"
  ]
}

delete_project disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  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.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_project tool do? +

Delete a project from QuantConnect. Args: project_id: The ID of the project to delete. Returns: A dictionary containing the deletion result. It is categorised as a Destructive tool in the QuantConnect MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_project? +

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

delete_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_project? +

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

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

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