MC-1 DOCS
API ReferenceCookbook
Docs/Agent Identity + Guard/Agent Identity + Agent Guard
PublishedGALAST REVIEWED · 30 AUG 2026

Agent Identity + Agent Guard

Bind agent actions to verified actors and bounded authority.

Overview

Identity establishes who or what is acting. Guard evaluates whether a requested tool action may proceed under current policy, permission, risk, and approval evidence.

  • Verify signed identity claims.
  • Use exact tool permissions such as tool:read_record.
  • Keep authority mission-bound and time-bound.
  • Deny or require approval before consequential execution.
  • Retain auditable decision context.

Production checklist

  • Keep credentials in a server-side secret store.
  • Set explicit cost, latency, privacy, provider, and regional constraints.
  • Capture route and evaluation evidence for incident review.
  • Test timeouts, cancellation, fallback, and denied-policy paths before rollout.
End of guide
Was this page helpful?