Are MCP tools broken in Workflows? #330
Replies: 1 comment 1 reply
-
|
I have similar issue. It seems to happen every now and then. Sometimes the tool call works and sometimes getting below error. The approval configuration for the tools does not seem to stick at all. In my workflow agent it asks me to approve every single tool call each time I test it no matter which option I have clicked before (approve once, always, all tools).
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am having troubles with my workflows, I had made a workflow that worked a few weeks ago. Now I wanted to call it from my local machine with the code that is supplied by it. I got an error saying that it couldn't wait for approval, which made sense to me. Time to turn on auto-approval. But then the workflow still didn't work, not even through the portal.
I simplified my workflow to just 1 agent invoke step now and the issue persists.
Test 1
I make a new agent that has 1 MCP tool and nothing else. I test the agent in the portal and it works for answering both regular questions and making tool calls. It will ask me for approval first by default and then approving it will do the tool call correctly.
Testing it in a workflow then means, first with a regular call that doesn't need a tool and it works fine. Ask for a tool call and it will ask for approval and then also give this type of error immediately:
However I can stll press approve, because the approval request is still in the debug screen. When I approve it will respond with:
Which makes sense I guess, considering the error we had before telling me it can't wait.
Test 2
When I then change it so my agent doesn't need approval anymore: so approval for all tools and testing it in the agent portal. Then the agent stops working, I need to specify allowed tools as well otherwise it can't access any tools it seems.
So I specify the 1 tool out of 3 (I also tried naming all tools in that field) that this MCP knows that this agent should use and set it to always approval all tools. Then it works again in the agent portal, it succesfully makes the tool call without asking for approval.
Going back to the workflow portal however now gives me this error:
In this case I also don't see any incoming ListToolsRequest in my MCP server, so it fails even earlier than with the previous case where it failed to wait for approval, but at least it knew which tool call to make. Now it seems to fail at the very start already.
Workflow info
It is the sequential example but then all but the first agentInvoke removed and then my specific test agent now selected. No other settings have been changed.
The text input I use in the workflow debug screen is exactly the same text I use to test my agent.
Is this some Azure AI foundry bug? Why can't the workflow invoke my agent anymore with its MCP tool? It used to work before, I have successfully ran workflows in the portal, where I still had to manually approve tool calls, but now that doesn't even work anymore either (see test 1)
TLDR:
Agent works with tool call when I just test the agent in the portal. Using that same agent in a workflow results in errors.
Beta Was this translation helpful? Give feedback.
All reactions