Locale fits teams that need an agent policy layer for MCP hosts, A2A-style delegation, and orchestrators that want stronger control over tool use without becoming execution platforms themselves.
An MCP-native host:
- calls
capabilities.get - verifies the token locally
- locally preflights covered
readandnetworkactions - calls
policy.evaluatefordeploy,write,commerce,identity,secrets, andadmin
A workflow engine:
- issues one capability token per mission
- distributes local verification and preflight to sub-agents
- attaches capability and decision artifacts to logs or receipts
This is the natural fit for A2A and multi-agent systems that need delegation with verifiable boundaries.
A platform team:
- runs the authority locally or in cloud
- manages declarative packs under source control
- validates integrations using host profiles, transcripts, chronology, and tests
A host team:
- replays golden transcripts
- validates named host profiles
- uses chronology and changelog to understand compatible changes over time
- MCP policy enforcement
- agent policy layer
- safe tool use for AI agents
- A2A and multi-agent governance
- offline verification and attestation for agent actions