Reassign work to another specialist AI agent and optionally spawn a new run. Also known as: handoff task, transfer work, change assignee. USE WHEN: a task needs to be reassigned to a different specialist agent. NEXT: Use get_agent_status to confirm the new agent picked up the task. DO NOT USE: fo...
AI agents invoke handoff_task to trigger actions in OrgX. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
note | string | — | Handoff note: what to do, constraints, context, definition of done |
agent | string | — | Target agent (e.g., "engineering-agent", "marketing-agent") |
spawn | boolean | — | If true (default), spawn a new agent run for the target agent |
task_id | string | — | Task UUID to hand off |
_context | object | — | Client context for conversation tracking (strongly recommended for cross-client continuity) |
Parameters from the server's own tool schema.
handoff_task 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.
Risk signalsHigh parameter count (21 properties)
Documented attack patterns abuse exactly the kind of access handoff_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OrgX, and nothing reaches the server without passing your rules. This is the rule we recommend for handoff_task:
{
"version": "1",
"default": "deny",
"tools": {
"handoff_task": {
"limits": [
{
"counter": "handoff_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}handoff_task 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.
Free to start. No card required.
Reassign work to another specialist AI agent and optionally spawn a new run. Also known as: handoff task, transfer work, change assignee. USE WHEN: a task needs to be reassigned to a different specialist agent. NEXT: Use get_agent_status to confirm the new agent picked up the task. DO NOT USE: for new tasks — use spawn_agent_task instead. It is categorised as a Execute tool in the OrgX MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
handoff_task accepts 5 parameters: note, agent, spawn, task_id, _context. The full parameter table on this page comes from the server's own tool schema.
Register the OrgX MCP server in PolicyLayer and add a rule for handoff_task: 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 OrgX. Nothing to install.
handoff_task 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 handoff_task 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 handoff_task. 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.
handoff_task is provided by the OrgX MCP server (useorgx/orgx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 OrgX tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 OrgX tools catalogued and risk-classified — across an index of 42,500+ MCP servers.