feat: resolve ArgumentEmail and ArgumentGroupName recipients at runtime

[dushyant-uipath]

Summary

Updates resolve_recipient_value() in escalation_tool.py to handle the two new argument-driven recipient types added in UiPath/uipath-python PR #1521. At runtime, each type's argument_path is looked up in the agent's input kwargs using dot-notation (safe_get_nested) to produce a concrete TaskRecipient.

Also fixes create_mcp_tools_from_agent — the function was incorrectly aliased to create_mcp_tools_and_clients (which takes list[AgentMcpResourceConfig]), but callers pass a LowCodeAgentDefinition. Replaced with a proper wrapper that extracts MCP resources from the agent definition first.

Changed files

File	Change
escalation_tool.py	resolve_recipient_value accepts optional input_args; ArgumentEmailRecipient and ArgumentGroupNameRecipient handling added; call site passes filtered agent input (internal graph state fields excluded)
escalate_action.py	Guardrails path also passes input_args to resolve_recipient_value — previously always raised ValueError for argument-based recipients
mcp/__init__.py + mcp_tool.py	create_mcp_tools_from_agent definition moved to mcp_tool.py with correct list[BaseTool] return type; re-exported from __init__.py
pyproject.toml	uipath>=2.10.49 (requires the companion PR to be merged)

Failure modes & what was tested

The only runtime failure path

In resolve_recipient_value():

value = safe_get_nested(input_args or {}, recipient.argument_path)
if value is None:
    raise ValueError(
        f"Argument '{recipient.argument_path}' has no value in agent input."
    )

This raises when:

1. The agent is invoked without the expected input argument (key missing)
2. The argument is present but explicitly None

This is intentional — a misconfigured escalation should fail loudly at task creation time, not silently create a task with no assignee.

There is no feature flag in the Python layer. The flag (EnableEscalationArgumentAssignee) lives in the frontend and Agents backend only. If the frontend sends an ArgumentEmail/ArgumentGroupName recipient (flag is on), the Python side always processes it. The frontend strips these types from the payload when the flag is off.

End-to-end local test (hacked-coded, 2026-04-15)

Agent configured with ArgumentEmail recipient (argument_path="assigneeEmail"), run against alpha:

uv run uipath run agent.json '{"assigneeEmail": "dushyant.pathak@uipath.com", "taskDescription": "Test dynamic assignee"}'

Action Center task created with:

recipient:
  type: TaskRecipientType.EMAIL
  value: dushyant.pathak@uipath.com   ← resolved from input arg at runtime ✓
title: Review Required
data.taskDetails: Test dynamic assignee

✓ Successful execution.

Other paths verified

• create_mcp_tools_from_agent loads without error — agents factory registers correctly ✓
• Existing AssetRecipient and StandardRecipient resolution paths unaffected ✓
• input_args=None default: all existing callers that don't pass input_args continue to work ✓
• escalate_action.py guardrails path: input_args now passed correctly, no longer raises on argument-based recipients ✓

Related

• Agents repo PR: UiPath/Agents#4835
• Data model PR: feat: add ArgumentEmail and ArgumentGroupName escalation recipient types uipath-python#1521 (must merge first)
• Design doc: https://uipath.atlassian.net/wiki/spaces/BPA/pages/90469990611/Dynamic+Assignee

Test plan

• ArgumentEmail recipient end-to-end: agent run with assigneeEmail input → Action Center task created with correct assignee ✓
• Same for ArgumentGroupName
• Run without the argument populated — verify ValueError with clear message
• Verify existing AssetRecipient and StandardRecipient paths unaffected
• Verify create_mcp_tools_from_agent no longer crashes when agent has MCP resources

[dianagrecu-uipath]

Please also add new tests to cover the new runtime code paths.

[radugheo]

The method resolve_recipient_value() is also called inside EscalateAction._create_task_node() in escalate_action.py, without input_args. For the new argument-based recipient types, this will always raise a ValueError since input_args defaults to {}.