请求任务交接。将任务转交给另一个 Agent。目标 Agent 需要调用 accept_handoff 或 reject_handoff。只有负责人或创建者可以发起交接。
AI agents use request_handoff to create or update resources in Agent-Comm-Hub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent-Comm-Hub environment.
This tool initiates a task handoff by transferring task ownership to another agent. It creates/modifies a task assignment record and triggers a workflow requiring the target agent to accept or reject. This is a reversible write operation (the handoff can be rejected), not destructive or financial. Severity is medium because misuse could disrupt task ownership and agent workflows.
From the tool's definition 请求任务交接。将任务转交给另一个 Agent。目标 Agent 需要调用 accept_handoff 或 reject_handoff。只有负责人或创建者可以发起交接。
Attacks that exploit this kind of access
请求任务交接。将任务转交给另一个 Agent。目标 Agent 需要调用 accept_handoff 或 reject_handoff。只有负责人或创建者可以发起交接。. It is categorised as a Write tool in the Agent-Comm-Hub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent-Comm-Hub MCP server in PolicyLayer and add a rule for request_handoff: 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 Agent-Comm-Hub. Nothing to install.
request_handoff is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the request_handoff 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 request_handoff. 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.
request_handoff is provided by the Agent-Comm-Hub MCP server (liuboacean/agent-comm-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →