team_work
让 AI 开发团队协作完成任务。团队包含前端专家、后端专家、QA专家,会智能分配任务并互相协作。
This record as markdown: /tools/7836246-claude-team-mcp/team-work.md
What team_work does on Claude Team MCP
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.
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 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
Attacks that exploit this kind of access
The rule that runs team_work safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Team MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For team_work, this is the rule to start with:
team_work 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Team MCP, apply this rule, and every team_work call is checked against it from then on.
Questions about team_work
让 AI 开发团队协作完成任务。团队包含前端专家、后端专家、QA专家,会智能分配任务并互相协作。. It is categorised as a Execute tool in the Claude Team MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude Team MCP server in PolicyLayer and add a rule for team_work: 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 Claude Team MCP. Nothing to install.
team_work is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the team_work 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 team_work. 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.
team_work is provided by the Claude Team MCP server (7836246/claude-team-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Team, and thousands of servers like it.
Across the catalogue