Compile a project in QuantConnect. Args: project_id: The ID of the project to compile. Returns: A dictionary containing the compilation result with compile ID, state, and logs.
AI agents invoke compile_project 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.
This is classified as Execute rather than Write because compilation is an active operation that triggers external processing and code evaluation, not merely data creation or modification. It represents an intermediate step in deploying trading strategies.
From the tool's definition The tool 'compile_project' triggers compilation of a trading strategy project, which executes code with external effects. In the context of QuantConnect (a trading platform), compilation is a prerequisite to running backtests and live algorithms.
Documented attack patterns abuse exactly the kind of access compile_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 compile_project:
{
"version": "1",
"default": "deny",
"tools": {
"compile_project": {
"limits": [
{
"counter": "compile_project_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}compile_project 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.
Compile a project in QuantConnect. Args: project_id: The ID of the project to compile. Returns: A dictionary containing the compilation result with compile ID, state, and logs. 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 compile_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.
compile_project 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 compile_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.
Set action: deny in the PolicyLayer policy for compile_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.
compile_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.
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.