拒绝任务交接。只有被请求的 target Agent 可以调用。拒绝后交接请求取消。
AI agents use reject_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 modifies data (handoff request state) but does not irreversibly delete it or execute arbitrary operations. The rejection is a status update that can theoretically be reversed by resubmitting a handoff. It affects multi-agent workflow coordination, so misuse could disrupt task assignments (medium severity), but the impact is limited to workflow state, not data loss or system compromise.
From the tool's definition Tool name is 'reject_handoff' and description states it rejects a task handoff request, canceling the handoff (拒绝任务交接). This modifies the state of a handoff/task request by transitioning it from pending to rejected—a reversible state change.
Attacks that exploit this kind of access
拒绝任务交接。只有被请求的 target Agent 可以调用。拒绝后交接请求取消。. 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 reject_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.
reject_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 reject_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 reject_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.
reject_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 →