Skip to content

Clarify validation before tool approval #427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
trymhaak wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify validation before tool approval #427

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions agent-framework/workflows/human-in-the-loop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,6 +304,9 @@ The `RequestPort` pattern described above works with custom executors and `Workf

Agents can use tools that require human approval before execution. When the agent attempts to call an approval-required tool, the workflow pauses and emits a `RequestInfoEvent` just like the `RequestPort` pattern, but the event payload contains a `ToolApprovalRequestContent` (C# and Go) or a `Content` with `type == "function_approval_request"` (Python) instead of a custom request type.

> [!IMPORTANT]
> Treat approval as scoped to the exact tool call in the request. Before sending an approval response, validate the requested function name and arguments against the application's allowlist and current authorization policy. If the call changes, require a new approval.

> [!TIP]
> For complete examples with code, see:
> - [Sequential orchestration with HITL](./orchestrations/sequential.md#sequential-orchestration-with-human-in-the-loop)
Expand Down