mcp__collaboration__wait_for_delegations
父会话用于收敛子会话结果的等待屏障：等待指定的 DutyDeck 协作子会话完成，并返回结构化结果摘要。只要本轮回复、决策或交付依赖已委派任务，主会话必须在回复前调用本工具，不能只因 delegate_agent/delegate_agents 已返回就宣称完成；需要全部结果时传入所有 delegationIds 并使用 mode=all，需要部分早期结果时才使用 mode=any。若返回 timeout 或仍有 running 委派，必须如实说明未收敛状态，不能把未完成任务当作已有结果。
This record as markdown: /tools/dutydeck/mcp--collaboration--wait-for-delegations.md
What mcp__collaboration__wait_for_delegations does on DutyDeck
AI agents invoke mcp__collaboration__wait_for_delegations to trigger actions in DutyDeck. 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 mcp__collaboration__wait_for_delegations is rated High
mcp__collaboration__wait_for_delegations triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs mcp__collaboration__wait_for_delegations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp__collaboration__wait_for_delegations, this is the rule to start with:
mcp__collaboration__wait_for_delegations 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 DutyDeck, apply this rule, and every mcp__collaboration__wait_for_delegations call is checked against it from then on.
Questions about mcp__collaboration__wait_for_delegations
父会话用于收敛子会话结果的等待屏障：等待指定的 DutyDeck 协作子会话完成，并返回结构化结果摘要。只要本轮回复、决策或交付依赖已委派任务，主会话必须在回复前调用本工具，不能只因 delegate_agent/delegate_agents 已返回就宣称完成；需要全部结果时传入所有 delegationIds 并使用 mode=all，需要部分早期结果时才使用 mode=any。若返回 timeout 或仍有 running 委派，必须如实说明未收敛状态，不能把未完成任务当作已有结果。. It is categorised as a Execute tool in the DutyDeck MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DutyDeck MCP server in PolicyLayer and add a rule for mcp__collaboration__wait_for_delegations: 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 DutyDeck. Nothing to install.
mcp__collaboration__wait_for_delegations 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 mcp__collaboration__wait_for_delegations 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 mcp__collaboration__wait_for_delegations. 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.
mcp__collaboration__wait_for_delegations is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
Across the catalogue