AI agents use lock_project_with_collaborators 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.
The tool changes project state by acquiring a lock, which is a reversible write operation on project metadata. It does not delete or destroy data (not Destructive), does not execute code (not Execute), and does not move money (not Financial). While it affects collaboration workflow, the core action is state modification.
From the tool's definition lock_project_with_collaborators: 'Lock a project so you can edit it.' This modifies the access state of a project, preventing concurrent edits by collaborators.
Documented attack patterns abuse exactly the kind of access lock_project_with_collaborators 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 lock_project_with_collaborators:
{
"version": "1",
"default": "deny",
"tools": {
"lock_project_with_collaborators": {
"limits": [
{
"counter": "lock_project_with_collaborators_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lock_project_with_collaborators 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.
Lock a project so you can edit it. 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 lock_project_with_collaborators: 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.
lock_project_with_collaborators 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 lock_project_with_collaborators 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 lock_project_with_collaborators. 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.
lock_project_with_collaborators 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.