AWS introduces Strands Box and Dogwood action-history authorization

Evidence record

Primary technical explanation of external interpreter, MCP and network policy enforcement, credential insertion, temporal rules and the documented direct-filesystem history gap.

Read the original source ↗

Claim-level citations (3)

• supportsStrands Box separates agent actions from policy enforcement, with a documented history gap: AWS says Strands Box combines OS containment with external Dogwood enforcement for shell, Python, MCP and outbound HTTP operations.

  Inside Strands Box; paragraphs on enforcement points and shared event history

• supportsStrands Box separates agent actions from policy enforcement, with a documented history gap: AWS states that direct filesystem paths granted in box.toml do not appear in Dogwood policy history, unlike file reads through the governed interpreters.

  Inside Strands Box; paragraph beginning "Policy sees the operations"

• supportsStrands Box separates agent actions from policy enforcement, with a documented history gap: AWS says its example Dogwood Slack rate-limit rule counts successful HTTP 200 responses in a ten-minute history and not denied or attempted posts.

  Temporal Policies: response status 200 matching and explanation of request versus response events