start_crew_run

SERVERUnClick SOURCE@unclick/mcp-server

High RISK CLASS

Category Execute

Parameters 42 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/start-crew-run.md

WHAT IT DOES

What start_crew_run does on UnClick

AI agents invoke start_crew_run to trigger actions in UnClick. 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.

Parameter	Type	Required	Description
`crew_id`	string	Yes	The UUID of the Crew to run
`task_id`	string	—	Client-generated idempotency key (UUIDv5 from thread_id + prompt_hash + time_bucket recommended). Required for safe retry. If omitted, the server creates a fres
`task_prompt`	string	Yes	The task the Council should deliberate on
`token_budget`	number	—	Optional token budget (default 150000)

Parameters from the server's own tool schema.

RISK

Why start_crew_run is rated High

This tool executes a complex workflow that initiates external processes (advisory requests, peer review, data persistence) rather than simply reading or writing discrete data. The effects are contingent on arguments (task_id, user context) and represent a triggered operation with side effects.

From the tool's definition Tool 'starts a Crews Council run' which 'prepares the run, asks advisors for opinions, runs peer review, persists the Chairman synthesis' — triggers a multi-step external operation (run preparation, peer review, persistence) whose effects depend on context…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_crew_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_crew_run, this is the rule to start with:

start_crew_run Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_crew_run": {
      "limits": [
        {
          "counter": "start_crew_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every start_crew_run call is checked against it from then on.

FAQ

Questions about start_crew_run

What does the start_crew_run tool do? +

Call this tool when the user wants to start a Crews Council run. In a sampling-capable MCP client, it prepares the run, asks advisors for opinions, runs peer review, persists the Chairman synthesis, and returns a ConversationalCard. If sampling is unavailable, the card reports SAMPLING_NOT_SUPPORTED. Response card surfaces was_duplicate when an existing run is returned for an already-seen task_id. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does start_crew_run accept? +

start_crew_run accepts 4 parameters: crew_id, task_id, task_prompt, token_budget. Required: crew_id, task_prompt. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on start_crew_run? +

Register the UnClick MCP server in PolicyLayer and add a rule for start_crew_run: 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 UnClick. Nothing to install.

What risk level is start_crew_run? +

start_crew_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_crew_run? +

Yes. Add a rate_limit block to the start_crew_run 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 start_crew_run completely? +

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

start_crew_run is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools → High-risk tools on this server →

Across the catalogue

run on 0sec →start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →shortcuts_run on Apple Apps MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →