---
schema_version: "newruntime-agent-readable-v0.2"
type: "capability_delta"
stable_id: "capability_delta:agent-access-is-becoming-identity-scoped-and-bounded"
slug: "agent-access-is-becoming-identity-scoped-and-bounded"
title: "Agent access is becoming identity-scoped and bounded"
description: "AWS documents spend attribution and cutoffs by IAM principal, while Clerk lets MCP users request additional scopes during a session. Together, they show controls moving from blanket access toward identity- and action-specific limits."
retrieval_nugget: "AWS documents spend attribution and cutoffs by IAM principal, while Clerk lets MCP users request additional scopes during a session. Together, they show controls moving from blanket access toward identity- and action-specific limits."
status: "published"
observed_at: "2026-11-15"
record_date: "2026-11-15"
date_kind: "observed_at"
before_capability: "Builders could grant agents access, but these items do not describe spend caps tied to agent identity or additional authorization scopes requested during a session."
enabling_change: "AWS guidance for Bedrock spend attribution and budget cutoffs per IAM principal, alongside Clerk’s session-time MCP scope requests."
after_capability: "Builders can attribute and limit agent spend by principal and request additional permissions for specific actions during a session."
human_consequence: "People can delegate work with more targeted controls instead of relying only on broad, one-time grants."
verification_level: "source-inspected"
buildability_class: "B2"
bottleneck: "The items describe separate controls, not a unified authorization flow; builders still need to connect identity, permissions, and spend limits in their own systems."
related_shift: "delegated-agent-identity"
related_posts: []
topics: ["github","mcp"]
source_urls: ["https://newruntime.com/signals/agent-spending-is-now-capped-per-identity-key-and-session-0a1354/","https://newruntime.com/signals/agent-authorization-is-becoming-action-specific-instead-of-a-one-time-fe039b/"]
featured: false
supporting_evidence: [{"title":"Agent spending is now capped per identity, key and session","url":"https://newruntime.com/signals/agent-spending-is-now-capped-per-identity-key-and-session-0a1354/","kind":"signal","observed_at":"2026-11-15"},{"title":"Agent authorization is becoming action-specific instead of a one-time grant","url":"https://newruntime.com/signals/agent-authorization-is-becoming-action-specific-instead-of-a-one-time-fe039b/","kind":"signal","observed_at":"2026-11-09"}]
routes: {"html":"https://newruntime.com/deltas/agent-access-is-becoming-identity-scoped-and-bounded/","markdown":"https://newruntime.com/deltas/agent-access-is-becoming-identity-scoped-and-bounded.md","json":"https://newruntime.com/deltas/agent-access-is-becoming-identity-scoped-and-bounded.json"}
source_format: "knowledge-ledger"
published_at: "2026-11-16T06:06:57.022Z"
auto_created: true
editorial_provenance: {"desk":"knowledge-revision","provider":"codex","model":"gpt-6-luna","created_at":"2026-11-16T06:06:57.022Z","week_start":"2026-11-09","review":"auto-created from reviewed evidence; the owner may revise or retire it"}
---

# Agent access is becoming identity-scoped and bounded

## Retrieval answer

AWS documents spend attribution and cutoffs by IAM principal, while Clerk lets MCP users request additional scopes during a session. Together, they show controls moving from blanket access toward identity- and action-specific limits.

## Capability change

- Before: Builders could grant agents access, but these items do not describe spend caps tied to agent identity or additional authorization scopes requested during a session.
- Enabling change: AWS guidance for Bedrock spend attribution and budget cutoffs per IAM principal, alongside Clerk’s session-time MCP scope requests.
- After: Builders can attribute and limit agent spend by principal and request additional permissions for specific actions during a session.

Human consequence: People can delegate work with more targeted controls instead of relying only on broad, one-time grants.

Bottleneck: The items describe separate controls, not a unified authorization flow; builders still need to connect identity, permissions, and spend limits in their own systems.

Buildability: B2. Verification: source-inspected. Related shift: [delegated-agent-identity](https://newruntime.com/shifts/delegated-agent-identity/).

These changes make identity more operational: AWS ties Bedrock spend to an IAM principal and can cut off access at a budget, while Clerk supports requesting additional MCP scopes during a session. Neither alone establishes a complete delegation system, but both support narrower controls around agent actions.

Build a flow that maps each agent to a principal, requests only needed scopes, and enforces a spend limit against that principal. Watch whether providers connect these controls directly and how clearly people can review or revoke them.

Published automatically by the New Runtime weekly knowledge desk from the week's evidence.

## Supporting evidence

- [Agent spending is now capped per identity, key and session](https://newruntime.com/signals/agent-spending-is-now-capped-per-identity-key-and-session-0a1354/) (signal, 2026-11-15)
- [Agent authorization is becoming action-specific instead of a one-time grant](https://newruntime.com/signals/agent-authorization-is-becoming-action-specific-instead-of-a-one-time-fe039b/) (signal, 2026-11-09)

## Provenance

Auto-created by the New Runtime weekly knowledge desk on 2026-11-16 from evidence reviewed in the week of 2026-11-09. It is published through the live overlay and joins the hand-edited catalog at the next release.
