Create an optimization with the specified parameters.
AI agents invoke create_optimization to trigger actions in QuantConnect MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating an optimization triggers computational execution of algorithmic trading strategy parameter sweeps on QuantConnect's platform. It is not a simple write of data — it initiates an active process (optimization run) that consumes compute resources and may influence subsequent live trading decisions. This falls under Execute rather than Write because it triggers external operations.
From the tool's definition 'Create an optimization with the specified parameters' on a platform that runs backtests, optimizations, and live trading algorithms
Attacks that exploit this kind of access
Create an optimization with the specified parameters. It is categorised as a Execute tool in the QuantConnect MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_optimization is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →