Menu

1 / 3

Step Functions as AI Agent Tools: The Model Decides When, the Workflow Decides How

DEV Community: aws·Matias Martinez·12 days ago
#1wRHlz3M
#devtoaws#devto#dev#gateway#agent
Reading 0:00
15s threshold

On October 29, 2026, AWS made it possible to expose existing AWS Step Functions workflows as tools for AI agents through Amazon Bedrock AgentCore Gateway. It sounds like just another integration, but it answers a question every team putting agents into production eventually hits: how much of a business process should the model be allowed to decide?

AWS's answer is a clean split. The agent decides when to start a process and with what input . How that process runs (step order, retries, approvals, timeouts) stays in a Step Functions definition you wrote, versioned and tested. The model cannot skip the manager approval step because it "seemed reasonable".

Who decides what when an agent calls a workflow through the connector (labels in Spanish). Diagram: CloudAcademy.ar.

TL;DR

AgentCore Gateway gets a managed connector ( connectorId: "states" ) that turns Step Functions API operations into MCP tools.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.