mcpcollaborationdelegate_agents

批量创建多个真实可见的 DutyDeck 协作子 Agent 会话。每个 item 可独立指定首轮 thinkingLevel；模型不支持时运行时会安全归一化。返回中的 configuredThinkingLevels/delegations[].thinkingLevel 表示各项配置/请求值，不代表模型 capability normalization 后的实际运行档位。

SERVERDutyDeck SOURCEtaokoplay/DutyDeck

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dutydeck/mcp--collaboration--delegate-agents.md

WHAT IT DOES

What mcpcollaborationdelegate_agents does on DutyDeck

AI agents call mcp__collaboration__delegate_agents to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mcpcollaborationdelegate_agents is rated Low

Even though mcp__collaboration__delegate_agents only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcpcollaborationdelegate_agents 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__delegate_agents, this is the rule to start with:

mcp__collaboration__delegate_agents Allowed

mcp__collaboration__delegate_agents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mcp__collaboration__delegate_agents": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mcpcollaborationdelegate_agents

What does the mcp__collaboration__delegate_agents tool do? +

How do I enforce a policy on mcp__collaboration__delegate_agents? +

Register the DutyDeck MCP server in PolicyLayer and add a rule for mcp__collaboration__delegate_agents: 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.

What risk level is mcp__collaboration__delegate_agents? +

mcp__collaboration__delegate_agents is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mcp__collaboration__delegate_agents? +

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

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

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

KEEP EXPLORING