create_project_collaborator · QuantConnect MCP Server MCP

WHAT IT DOES

What create_project_collaborator does on QuantConnect MCP Server

AI agents use create_project_collaborator to create or update resources in QuantConnect MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuantConnect MCP Server environment.

WHY IT NEEDS A POLICY

Why create_project_collaborator needs a policy

This tool creates a new access control relationship by adding a collaborator to a project. This is a reversible write operation (collaborators can be removed) that modifies project metadata and permissions. It does not execute code, delete data, move money, or read data without side effects.

From the tool's definition Tool name 'create_project_collaborator' and description 'Add a collaborator to a project' indicate creation of a new collaborator assignment, which modifies project access control settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_project_collaborator Rate-limited

create_project_collaborator 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_project_collaborator": {
      "limits": [
        {
          "counter": "create_project_collaborator_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches QuantConnect MCP Server, so you can run agents against it safely.

FAQ

Questions about create_project_collaborator

What does the create_project_collaborator tool do? +

Add a collaborator to a project. It is categorised as a Write tool in the QuantConnect MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_project_collaborator? +

Register the QuantConnect MCP Server MCP server in PolicyLayer and add a rule for create_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 MCP Server. Nothing to install.

What risk level is create_project_collaborator? +

create_project_collaborator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_project_collaborator? +

Yes. Add a rate_limit block to the create_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.

How do I block create_project_collaborator completely? +

Set action: deny in the PolicyLayer policy for create_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.

What MCP server provides create_project_collaborator? +

create_project_collaborator is provided by the QuantConnect MCP Server MCP server (mymanish9-code11/quantconnect-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.