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.
The description is empty, so classification is based on the tool name and server context. 'create_optimization' on a quantitative trading platform likely launches an optimization job (e.g., parameter sweep/backtesting optimization), which constitutes executing a computational process. Sibling tools like 'create_backtest' and 'create_live_algorithm' confirm this server runs trading algorithms.
From the tool's definition Tool name 'create_optimization' on a trading platform server described as 'LLM Driven Trading Platform Orchestration - Strategy Design, Research & Implementation'
Documented attack patterns abuse exactly the kind of access create_optimization 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 create_optimization:
{
"version": "1",
"default": "deny",
"tools": {
"create_optimization": {
"limits": [
{
"counter": "create_optimization_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} create_optimization stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_optimization. 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 (taylorwilsdon/quantconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.