AIUC-1
Prepare evidence for selected AIUC-1 controls.
AIUC-1 includes requirements for restricting unsafe tool calls and assigning accountability. The records below may support review when combined with implementation and operational evidence.
AIUC-1 D003: Restrict unsafe tool calls AIUC-1 E004: Assign accountabilitySelected-control guide reviewed September 9, 2026. This mapping does not assert AIUC-1 certification or satisfaction of the full standard.
What the evidence can contribute.
Permission Protocol’s suggested mappings below are for review. Confirm the fields available in your integration and whether the artifact is independently signed. Authorization evidence alone does not prove execution, complete coverage, or compliance.
D003: tool-call safeguards
- Potential receipt or decision evidence
- Tool rules, decision logs, and approval evidence for calls inside the configured boundary.
- Your team must establish
- Implement and test authorization, validation, monitoring, and applicable limits. A decision record does not enforce rate or transaction limits.
D003: human review
- Potential receipt or decision evidence
- A human decision tied to the action reviewed, where the integration supplies that record.
- Your team must establish
- Define sensitive operations, enable an appropriate approval workflow, and test denials and timeouts.
E004: accountability
- Potential receipt or decision evidence
- A named approver and policy reference can support traceability for an individual action.
- Your team must establish
- Assign organizational accountability and document the roles and responsibilities required by the standard.
Build an evidence pack for one workflow.
Agree the requirement with your reviewer. Collect the configuration, approval records, verification results, exception handling, and tests for the chosen path. Evaluate gaps before expanding.