Fixed: No approval response was provided for this approval required tool call
I approved a tool call over AG-UI exactly the way the interrupt asked, "approved": true, and the tool still didn't run. Its result said: Tool call invocation was rejected by the approver and must not be retried. No approval response was provided for this approval required tool call. The approval needs one more thing that nothing in the interrupt mentions.
What I Was Doing
I was adding a password reset that needs approval to an IT service desk agent: an ASP.NET Core API that serves a Microsoft Agent Framework agent over AG-UI with MapAGUIServer. The tool is wrapped in ApprovalRequiredAIFunction, so when the model calls it, the run ends with an interrupt instead of a reset, and the employee answers in the next request. That's Part 13 of the IT Service Desk series.
To show it in the smallest program, here is the same thing in a coffee-order API with one tool, place_order, wrapped the same way and served the same way. The packages are Microsoft Agent Framework's Microsoft.Agents.AI.Hosting.AGUI.AspNetCore and Microsoft.Agents.AI.Foundry 1.28.0-preview.261106.1. The order request ended as it should:
data: {"type":"RUN_FINISHED","threadId":"order-3","runId":"run-1","outcome":{"type":"interrupt","interrupts":[{"id":"ficc_call_HitbfGV41MSfDyndCBVQbFAx","reason":"tool_call","message":"Approval required for tool call: place_order","toolCallId":"call_HitbfGV41MSfDyndCBVQbFAx","responseSchema":{"type":"object","properties":{"approved":{"type":"boolean"}},"required":["approved"]}}]},"usage":[…]}
The interrupt's responseSchema describes the answer it wants: an object with one required property, approved, a boolean.
What I Expected
AG-UI answers an interrupt with a resume entry in the next run of the same thread. I sent the shape the schema describes:
{
"threadId": "order-3",
"runId": "run-2",
"parentRunId": "run-1",
"messages": [],
"resume": [
{
"interruptId": "ficc_call_HitbfGV41MSfDyndCBVQbFAx",
"status": "resolved",
"payload": { "approved": true }
}
]
}
I expected place_order to run, a TOOL_CALL_RESULT with the order, and the agent confirming it.
What I Got
The run went through, but the tool didn't run:
data: {"type":"RUN_STARTED","threadId":"order-3","runId":"run-2","parentRunId":"run-1"}
data: {"type":"TOOL_CALL_START","toolCallId":"call_HitbfGV41MSfDyndCBVQbFAx","toolCallName":"place_order","parentMessageId":"ec2f4532d1e74ec1bc48c7308c6ae7ae","rawEvent":{…}}
data: {"type":"TOOL_CALL_ARGS","toolCallId":"call_HitbfGV41MSfDyndCBVQbFAx","delta":"{\"drink\":\"flat white\",\"cups\":2}","rawEvent":{…}}
data: {"type":"TOOL_CALL_END","toolCallId":"call_HitbfGV41MSfDyndCBVQbFAx","rawEvent":{…}}
data: {"type":"TOOL_CALL_RESULT","messageId":"call_HitbfGV41MSfDyndCBVQbFAx","toolCallId":"call_HitbfGV41MSfDyndCBVQbFAx","content":"Tool call invocation was rejected by the approver and must not be retried. No approval response was provided for this approval required tool call.","rawEvent":{…}}
… the agent's answer, "I couldn't place the order." …
data: {"type":"RUN_FINISHED","threadId":"order-3","runId":"run-2","outcome":{"type":"success"},"usage":[…]}

The approval turned into a rejection. The service desk did the same: the reset didn't run, and the agent told the employee it couldn't complete it.
What I Checked
1. The API's console. Nothing: no warning, no error. The run ended with success, so from the outside everything looked fine except the result.
2. The message. It has two sentences. The first is the text every rejected call gets. The second, No approval response was provided for this approval required tool call, says the agent never received my answer at all, so it rejected the waiting call on its own.
3. Microsoft's documentation. The C# guide for human-in-the-loop with AG-UI shows the server side and a .NET client that answers with request.CreateResponse(approved: true), then says: The adapter converts the MAF response to the canonical AG-UI resume payload. It doesn't show that payload for .NET. The Python section of the same page shows one, but with accepted, while the .NET interrupt asks for approved. So the documentation didn't say what the .NET server expects.
4. Which AG-UI library the server uses. Learn says MapAGUIServer uses the AG-UI .NET SDK. The package's dependencies in microsoft.agents.ai.hosting.agui.aspnetcore.nuspec name it:
<dependency id="AGUI.Server" version="1.0.0" />
5. The source of that version. AGUI.Server 1.0.0's package records the commit it was built from, f08ccf8, in the official ag-ui-protocol/ag-ui repository. In that commit, RunAgentInputExtensions.cs turns each resume entry into the agent's input, and explains how in a comment:
// Tool-approval-shaped resume payloads (with a `toolCall` field) become a
// ToolApprovalRequestContent + ToolApprovalResponseContent pair so
// FunctionInvokingChatClient resumes the tool naturally; everything else becomes
// a generic InterruptResponseContent.
And the check itself, in TryDecodeToolApprovalResume:
if (resume.Payload is not { ValueKind: JsonValueKind.Object } element
|| !element.TryGetProperty("toolCall", out _))
{
return false;
}
A payload without toolCall isn't treated as an approval.
6. Whether it's known. It is: issue #2815, [dotnet] Tool-approval resume without toolCall echo degrades to generic interrupt, reported against AGUI.Server 1.0.0 through Agent Framework's hosting package. Its repro is my request, and it says the same request with payload:{approved:true, toolCall:{callId, name, arguments}} succeeds end to end. The reporter used an older Agent Framework hosting package, 1.22.0-preview.260918.1, where the run ended with a RUN_ERROR; with 1.28.0, the waiting call is rejected instead, as above. The issue is closed, and the fix is in the repository's source.
7. Whether a release has the fix. NuGet's newest AGUI.Server is 1.0.1. Its package records commit 9a7508f, and GitHub's comparison of the fix commits with it says diverged: 1.0.1 was built without them. No released version has the fix yet, and Agent Framework's hosting package depends on 1.0.0 anyway.
Why It Happens
The interrupt's responseSchema describes the decision, approved. But AGUI.Server 1.0.0 rebuilds the approval from the payload: it needs the tool call too, to create the ToolApprovalRequestContent and ToolApprovalResponseContent pair that Agent Framework's function calling understands. Without toolCall, the answer arrives as a generic interrupt response that nothing matches to the waiting call. The function-calling layer then finds a call that is waiting for approval with no answer, and rejects it with the message above. That's also why the console stays quiet: from its point of view, nothing went wrong.
The Fix
Send the tool call in the payload, next to approved. Its three values come from the interrupted run's events: callId is the interrupt's toolCallId, name is the tool, and arguments are the ones from TOOL_CALL_ARGS, as a JSON object:
{
"threadId": "order-5",
"runId": "run-2",
"parentRunId": "run-1",
"messages": [],
"resume": [
{
"interruptId": "ficc_call_SUn4g8Lp3RxZmQaaM9zUtBjK",
"status": "resolved",
"payload": {
"approved": true,
"toolCall": {
"callId": "call_SUn4g8Lp3RxZmQaaM9zUtBjK",
"name": "place_order",
"arguments": { "drink": "flat white", "cups": 2 }
}
}
}
]
}
That's also what AG-UI's own .NET client, AGUIChatClient, sends when it turns a ToolApprovalResponseContent into a resume entry, and the fixed source still accepts it. A rejection uses the same shape with "approved": false.
After the Fix
A new order, answered with the fixed payload:
data: {"type":"TOOL_CALL_RESULT","messageId":"call_SUn4g8Lp3RxZmQaaM9zUtBjK","toolCallId":"call_SUn4g8Lp3RxZmQaaM9zUtBjK","content":"\"Order 1042 is placed: 2 x flat white.\"","rawEvent":{…}}
data: {"type":"RUN_FINISHED","threadId":"order-5","runId":"run-2","outcome":{"type":"success"},"usage":[…]}

The tool ran, and the agent answered Your order is placed: 2 flat whites. Order number **1042**. In the service desk, the same change made the password reset run.
Common Mistakes
| Mistake | What happens | Do this instead |
|---|---|---|
Following the interrupt's responseSchema alone | The approval becomes a rejection | Add toolCall to the payload |
Sending arguments as a string, the way TOOL_CALL_ARGS shows it | arguments is a JSON object in the payload | Paste the arguments without the backslashes and the outer quotes |
Reading the run's success as proof the tool ran | The run succeeds even when the call was rejected | Look for a TOOL_CALL_RESULT with the tool's real result |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| The tool's result is Tool call invocation was rejected by the approver and must not be retried. No approval response was provided for this approval required tool call. after an approval | The payload has no toolCall | Send the payload from The Fix |
| The same message after sending a new chat message | A new message instead of an answer: the waiting call is rejected | Answer the interrupt with a resume entry instead |
| The result is only Tool call invocation was rejected by the approver and must not be retried. | The answer arrived, with "approved": false | That's a rejection working as it should |
FAQ
Do I need this with the AG-UI .NET client?
No. AGUIChatClient builds the resume entry from request.CreateResponse(...), and it sends the toolCall with it. You need the fix when you write the resume entry yourself: from an .http file, a JavaScript client or a server route that builds AG-UI requests.
Will this break when AG-UI releases the fix?
The source with the fix still reads payloads that have a toolCall, and also accepts payloads without one. Sending it keeps working either way.
Can the toolCall change what gets approved?
No. When I sent an approval with "cups": 10 for a call the model made with "cups": 2, the order was placed for two. Agent Framework runs the call that is waiting, and the toolCall only lets the server recognize the answer.
Conclusion
No approval response was provided for this approval required tool call means the agent never received the approval. With AGUI.Server 1.0.0, which Microsoft Agent Framework's AG-UI hosting package uses, a resume payload counts as an approval only when it carries the toolCall: callId, name and arguments, next to approved. Add it, and the approved tool runs.
Additional Resources
- AG-UI issue #2815 — the bug, its repro and the fix in the source.
- Human-in-the-Loop with AG-UI — approvals over AG-UI in Agent Framework.
- Using function tools with human in the loop approvals —
ApprovalRequiredAIFunctionand the approval types.
