AI agents use update_backtest to create or update resources in QuantConnect — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuantConnect environment.
This tool updates backtest metadata reversibly without deleting or destroying data, and carries no financial impact. The blast radius is limited to changing human-readable labels/descriptions on a backtest object. Classified as Write (low severity) rather than Execute because it performs a metadata update operation, not execution of code or external operations.
From the tool's definition Tool description states 'Update the name or note of a backtest' — modifies metadata (name/note) of an existing backtest resource.
Documented attack patterns abuse exactly the kind of access update_backtest gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and QuantConnect, and nothing reaches the server without passing your rules. This is the rule we recommend for update_backtest:
{
"version": "1",
"default": "deny",
"tools": {
"update_backtest": {
"limits": [
{
"counter": "update_backtest_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_backtest stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Update the name or note of a backtest. It is categorised as a Write tool in the QuantConnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QuantConnect MCP server in PolicyLayer and add a rule for update_backtest: 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. Nothing to install.
update_backtest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_backtest 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 update_backtest. 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.
update_backtest is provided by the QuantConnect MCP server (quantconnect/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 64 QuantConnect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
64 QuantConnect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.