Delete an optimization.
AI agents call delete_optimization 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.
This tool permanently removes an optimization object from the QuantConnect platform. Optimizations represent potentially valuable computational work and parameter tuning results. Deletion cannot be undone, making this Destructive rather than Write. While not directly moving funds, in a financial trading context, loss of optimization work could indirectly impact trading decisions.
From the tool's definition Tool name is 'delete_optimization' with description 'Delete an optimization.' The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an optimization. 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.
Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for delete_optimization: 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.
delete_optimization is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_optimization 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 delete_optimization. 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.
delete_optimization 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 →