AIToday
AI Safety & AlignmentLarge Language ModelsAmazon AI BlogPublished: Aug 7, 2026, 04:01 JST3 min read

Amazon Bedrock adds session-aware security rules for AI agents

Amazon Bedrock adds session-aware security rules for AI agents

Key takeaway

  • Amazon Bedrock AgentCore now offers temporal policies, security rules that track an AI agent's session history and make authorization decisions based on the full sequence of prior actions.

  • This addresses a key vulnerability: stateless access controls can miss harmful patterns that only become apparent when looking at an agent's trajectory over time.

  • Temporal policies run at the gateway perimeter outside the agent's code, preventing circumvention.

3 Key Points

  1. What happened

    Amazon introduced temporal policies in Bedrock AgentCore, a security layer that tracks and evaluates an AI agent's decision history at the gateway level. Unlike traditional stateless access controls, temporal policies can see the full sequence of actions a session has taken and block tool calls based on prior context—for example, preventing an agent from using a hallucinated account number after reading from an untrusted source.

  2. Why it matters

    AI agents decide at runtime which actions to take in what order, making them harder to control than conventional applications. A single tool call might look safe in isolation but harmful in context (e.g., after reading bad data). Temporal policies run outside the agent's own code, so the agent cannot bypass or manipulate them regardless of how it is prompted or if bugs exist in its code.

  3. What to watch

    The example shows practical use cases: enforcing tool-call order (e.g., fetch client profile before executing a trade), requiring market prices be fetched within 1 minute of a trade, capping session exposure (e.g., $60,000 total trade value), and requiring human approval for trades over $25,000. Temporal policies are written in Dogwood, a new open-source governance language that remains compatible with existing Cedar policies.

Ask the AI about this article →

Context & Analysis

AI agents introduce a new security challenge that traditional access controls cannot fully address. In conventional applications, business logic deterministically enforces the correct order and state of operations; each action can be evaluated independently. AI agents, by contrast, decide at runtime which tools to call, with which arguments, and in what order. A tool call that appears safe when viewed in isolation can become dangerous in context—for example, an agent that retrieves an account number from an untrusted source might hallucinate a different number before passing it to a transfer function, or a runaway agent might execute dozens of trades in a loop, accumulating exposure that exceeds policy limits, with no mechanism to track the session total.

Temporal policies address this gap by introducing stateful authorization at the gateway layer. They evaluate each request not just on its own merits but in the context of the agent's trajectory—the ordered sequence of actions taken within a session. Because these policies operate outside the agent's code, at the AgentCore Gateway perimeter, they cannot be bypassed or manipulated by the agent itself, regardless of prompting or implementation bugs. The example workflow in a private banking scenario illustrates the practical power: enforcing that a client profile is fetched before a portfolio is loaded, and that a portfolio loaded in one call matches exactly the portfolio ID passed to a trade execution call, prevents common failure modes while allowing the agent flexibility in how it reaches its goal.

FAQ

How does temporal policy enforcement prevent the agent from bypassing it?
Temporal policies run at the AgentCore Gateway perimeter, outside the agent's own code. Because they operate at this gateway layer, the agent cannot intercept, manipulate, or alter the policy logic or state store, regardless of how it is prompted or what bugs exist in the agent's code.
What is a session and how long does the history last?
A session is identified by a session ID combined with the end user's identity, and you define what constitutes the beginning and end of a session (a single conversation, multi-step task, or longer workflow). Within an active session, agent trajectories carry a maximum look-back window of 24 hours; any events older than that are automatically deleted.
What is Dogwood and why does it matter?
Dogwood is a new open-source governance language designed for agents and their tools. It supports evaluating existing Cedar policies and enables support for temporal conditions. Because Dogwood is compatible with existing Cedar policies, customers can continue to use their current Cedar policies without needing to migrate.
Amazon AI BlogRead Original Article

Get the latest AI Safety & Alignment news every morning

For example, today's edition would include:

  • AI agent security startup AIR raises $50M from stealthTechCrunch AI · 44m ago
  • Google AI Search flags Facebook users as dangerTHE DECODER · 3h ago
  • Pentagon deploys ChatGPT MilITmedia AI+ · 6h ago

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

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleU.S., China race for humanoid robot dominance