AgentCore adds two controls beyond one tool call

Amazon Bedrock AgentCore added 2 gateway controls—temporal policies and rate limiting—to govern an agent across a sequence of actions rather than judging each tool call alone. AWS’s launch notice says policies can enforce call order, bind a new argument to an earlier result, require human approval, and cap requests, inference tokens, or concurrent connections by OAuth or IAM identity. For teams following the shift toward runtime policy inside agent harnesses, the useful signal is architectural: budgets and approval state are moving out of prompts and application code into the gateway.