Server policies
Bind scopes, tenant trust, delegation, and skills policy to the operation being protected.
Define policy at the action boundary. Scope requirements come from your application, not the incoming token. Trust the configured issuer keys and expected audience, then compare verified grants against the required operation.
Layers
- ACT verifies signed capability claims and required scope.
- Arsenal evaluates credential/proxy requests against tenant policy and consent.
- AEGIS provides composition, spending, temporal, lineage and contract evaluators.
- Skills governance gates specific declared tool/skill invocations.
An authenticated request can still be denied by policy. A permitted skill does not imply permission to use every credential or mutate every tenant. Delegation must preserve scope and depth restrictions rather than expanding the parent's authority.
Exercise missing policy, nonmatching policy, expired capability, wrong audience, revoked authority, and missing consent. Record denials distinctly from configuration failures. See Arsenal policy, AEGIS policy, and skills governance.