# team_work

让 AI 开发团队协作完成任务。团队包含前端专家、后端专家、QA专家，会智能分配任务并互相协作。

Agent View of the PolicyLayer registry record for `team_work`. HTML page: https://policylayer.com/tools/7836246-claude-team-mcp/team-work

## Facts

- Tool: `team_work`
- Server: Claude Team MCP (`7836246/claude-team-mcp`) — https://policylayer.com/tools/7836246-claude-team-mcp.md
- Homepage: https://github.com/7836246/claude-team-mcp
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "team_work",
    "arguments": {}
  }
}
```

## Why team_work is rated High

This tool orchestrates multiple AI agents to autonomously execute complex development tasks with intelligent task distribution. It triggers external operations (code generation, review, QA) whose effects depend on arguments. Since it can spawn and coordinate multiple agents executing arbitrary development work, it falls under Execute.

From the tool's own definition: "'让 AI 开发团队协作完成任务' (let the AI development team collaborate to complete tasks) — triggers intelligent task distribution and multi-agent coordination across frontend, backend, and QA experts"

## Use case

AI agents invoke team_work to trigger actions in Claude Team MCP. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Claude Team MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "team_work": {
      "limits": [
        {
          "counter": "team_work_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Claude Team MCP (17)

- `fix_bug` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/fix-bug.md
- `run_workflow` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/run-workflow.md
- `analyze_project_structure` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/analyze-project-structure.md
- `ask_expert` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/ask-expert.md
- `code_review` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/code-review.md
- `cost_estimate` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/cost-estimate.md
- `explain_plan` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/explain-plan.md
- `history_context` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-context.md
- `history_get` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-get.md
- `history_list` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-list.md
- `history_search` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-search.md
- `list_workflows` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/list-workflows.md
- `read_project_files` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/read-project-files.md
- `suggest_workflow` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/suggest-workflow.md
- `team_dashboard` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/team-dashboard.md
- `usage_stats` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/usage-stats.md
- `generate_commit_message` — Write — https://policylayer.com/tools/7836246-claude-team-mcp/generate-commit-message.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=7836246-claude-team-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/7836246-claude-team-mcp