Skip to main content
KavachOS tracks the two emerging IETF drafts for agent authorization: draft-goswami-agentic-jwt-00 (agentic JWT claims) and draft-liu-agent-operation-authorization-01 (three-layer user-workload-token binding). Claim names are defined in a single file so future audits are a one-file review.

The claim constants

Every claim name lives in packages/core/src/standards/claims.ts as AGENTIC_JWT_CLAIMS. Each constant has a JSDoc reference to the relevant draft section.

Turning claim emission on

Claim emission is off by default. Flip the emitAgenticJwtClaims flag on your Kavach config to start populating claims on issued JWTs:
With the flag on, a JWT issued for a delegated agent looks like this (abridged):

What is populated today

Roadmap

  • Three-layer binding (wit, operation): coming with workload identity support.
  • act and may_act for RFC 8693 delegation chains: coming with the delegation chain refactor.
  • Auto-populated trust_tier on the MCP token path without manual context wiring: follow-up.

What this does not aim at

  • OpenID for Verifiable Presentations (OID4VP). Out of scope for agent sign-in. Verifiable Credentials KavachOS issues are for audit, not for sign-in.
  • SPIFFE URI scheme. Agent identity uses DIDs (did:key, did:web) which fit the hosted path better.
  • Post-quantum signatures (ML-DSA). Tracked, not scheduled.
Last modified on April 18, 2026