
Amazon Bedrock AgentCore has introduced temporal policies, a new security layer that controls AI agent behavior by evaluating requests against an agent's session history rather than treating each action independently.
Because AI agents decide at runtime which tools to call and in what order, traditional stateless access controls cannot catch problems that only emerge in context—such as an agent hallucinating a different account number after reading data.
Temporal policies run at the gateway perimeter, outside the agent's code, and enforce rules like requiring a client profile lookup before portfolio access, matching trade amounts to client profiles, requiring human approval for trades over $25,000, and capping total session trade value at $60,000.
What happened
Amazon Bedrock AgentCore introduced temporal policies, a new security feature that enforces authorization rules based on an AI agent's session history rather than treating each action in isolation. These policies run at the gateway perimeter, outside the agent's code, and evaluate requests against prior events in the agent's trajectory to determine whether to allow or deny them.
Why it matters
AI agents decide at runtime which tools to call and in what order, making traditional stateless access controls insufficient. A single tool call might be safe alone but harmful in context—for example, an agent could hallucinate a different account number after reading data and pass it to a transfer tool. Temporal policies prevent such issues by enforcing workflow sequencing, preventing data fabrication between tool calls, capping cumulative financial exposure, and requiring human approval for high-value actions, which is critical for financial services and other regulated use cases.
What to watch
The feature is built on Dogwood, a new open-source governance language designed for agents that is compatible with existing Cedar policies, so customers can use their current policies without migration. Temporal policies run at the AgentCore Gateway and can govern Model Context Protocol (MCP) tool calls, agent-to-agent calls, and model inference calls through a single consistent enforcement point.
Ask the AI about this article →
AI agents present a fundamentally different security challenge than traditional applications. While conventional software relies on deterministic business logic to enforce the correct sequence of actions and data freshness, AI agents decide at runtime which tools to call, in what order, and with which arguments. This flexibility, combined with increasingly capable models, creates scenarios where a single tool call appears safe in isolation but becomes harmful when considered in the context of prior actions—such as an agent hallucinating a different account number after reading from an untrusted data source, or executing dozens of trades in a loop without tracking cumulative exposure.
Amazon's temporal policies extend the existing stateless policy engine in AgentCore by introducing trajectory awareness. A trajectory is the ordered sequence of actions within a session, and temporal policies evaluate the current request against that history. By running at the gateway perimeter rather than within the agent's code, these policies cannot be bypassed or manipulated by the agent itself. This architectural choice is critical: agents never see the policy logic, never touch the state store, and cannot alter the controls.
The feature is built on Dogwood, a new open-source governance language designed for agents and compatible with existing Cedar policies, allowing customers to migrate gradually. For financial services firms managing AI agents that handle client portfolios, temporal policies address compliance requirements: enforcing that advisors retrieve client profiles and load portfolios before trades, that the portfolio ID in a trade matches the client profile output, that market prices are retrieved within 1 minute of trade execution, and that any trade over $25,000 requires explicit advisor approval. Sessions are bounded by a 24-hour look-back window, and sessions are uniquely identified by combining a session ID with the end user's identity, ensuring policies apply independently to each trajectory based on underlying identity.
For example, today's edition would include:
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. Q&As are published on this page for other readers too.
Visko raised $10 million in pre-seed funding from Llama Ventures and opened public access to its first foundat…
AI company Runway has unveiled Solaris, the first model in a new category it calls "Interface World Models." I…

Google's AI search gave advice to call emergency services for users alone with an African, Indian, or Pakistan…

John Deere introduced JD, a conversational AI tool that lets farmers ask open-ended questions about their hist…

Nvidia CEO Jensen Huang said on Fox Business that AI is creating 'hundreds of thousands' of jobs, including in…

Israeli startup DataAgent Ltd