Remove a collaborator from a project.
AI agents call delete_project_collaborator to permanently remove resources in QuantConnect — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a collaborator from a project is a destructive action: it revokes that user's access and cannot be undone without re-inviting them. No financial movement is involved, but the action is irreversible in its immediate effect, placing it in the Destructive category. Severity is medium since it affects collaboration access rather than data or code assets directly.
From the tool's definition 'Remove a collaborator from a project' — removal of a collaborator is an irreversible action that revokes access
Documented attack patterns abuse exactly the kind of access delete_project_collaborator 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 delete_project_collaborator:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project_collaborator"
]
}delete_project_collaborator disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a collaborator from a project. It is categorised as a Destructive tool in the QuantConnect MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the QuantConnect MCP server in PolicyLayer and add a rule for delete_project_collaborator: 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.
delete_project_collaborator is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_project_collaborator 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 delete_project_collaborator. 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.
delete_project_collaborator 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.