Domain 03Introduced in v1.0

Tool and API Governance

L1L2L328 ACRs (28 defined in current release)

Summary#

Tool invocation controls, permission scope, and API validation

Applicability#

Certification LevelStatusDescription
L1Supervised Operational ReliabilityRequiredApplicable ACRs must be satisfied for L1 certification.
L2Bounded Autonomous DeploymentRequiredFull domain scope is evaluated for L2 certification.
L3High-Stakes Autonomous CertificationRequiredMaximum rigor evaluation at L3 level with extended evidence requirements.

Risk Rationale#

Linked ACR Controls#

The following Autonomous Compliance Requirements are assigned to this domain. Each ACR defines a specific, testable control with its own evaluation method, classification, and evidence requirements.

ACR-3.01

All tool invocations SHALL be authorized against a documented tool access policy.

All tool invocations SHALL be authorized against a documented tool access policy.

AT+EI|Risk weight: 5/10|
L1L2L3
ACR-3.02

The system SHALL prevent unauthorized tool chaining where the output of one tool triggers another wi

The system SHALL prevent unauthorized tool chaining where the output of one tool triggers another without explicit authorization.

ATAutomated Testing|Risk weight: 5/10|
L1L2L3
ACR-3.03

A tool registry SHALL document all authorized tools, their capabilities, access conditions, and risk

A tool registry SHALL document all authorized tools, their capabilities, access conditions, and risk classifications.

EIEvidence Inspection|Risk weight: 4/10|
L1L2L3
ACR-3.04

Tool access SHALL follow the principle of least privilege, granting only the minimum capabilities re

Tool access SHALL follow the principle of least privilege, granting only the minimum capabilities required for each operation.

AT+EI|Risk weight: 4/10|
L1L2L3
ACR-3.05

Rate limiting SHALL be enforced for all tool invocations with configurable limits per tool and per t

Rate limiting SHALL be enforced for all tool invocations with configurable limits per tool and per time period.

AT+CM|Risk weight: 3/10|
L1L2L3
ACR-3.06

Abuse detection mechanisms SHALL identify anomalous tool usage patterns including unusual frequency

Abuse detection mechanisms SHALL identify anomalous tool usage patterns including unusual frequency and unexpected parameters.

AT+CM|Risk weight: 4/10|
L1L2L3
ACR-3.07

External tool outputs SHALL be validated and sanitized before incorporation into system decisions.

External tool outputs SHALL be validated and sanitized before incorporation into system decisions.

ATAutomated Testing|Risk weight: 5/10|
L1L2L3
ACR-3.08

Tool output validation SHALL include schema validation, range checking, and format verification.

Tool output validation SHALL include schema validation, range checking, and format verification.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3
ACR-3.09

Tool output sanitization SHALL prevent injection attacks propagated through tool responses.

Tool output sanitization SHALL prevent injection attacks propagated through tool responses.

ATAutomated Testing|Risk weight: 5/10|
L1L2L3
ACR-3.10

The system SHALL detect anomalous tool response sizes, latencies, and error rates.

The system SHALL detect anomalous tool response sizes, latencies, and error rates.

AT+CM|Risk weight: 3/10|
L1L2L3
ACR-3.11

Tool invocation audit trails SHALL record the invoking context, parameters, response, and downstream

Tool invocation audit trails SHALL record the invoking context, parameters, response, and downstream actions.

AT+EI|Risk weight: 4/10|
L1L2L3
ACR-3.12

Tool invocations SHALL include timeout mechanisms with defined maximum execution durations.

Tool invocations SHALL include timeout mechanisms with defined maximum execution durations.

ATAutomated Testing|Risk weight: 3/10|
L1L2L3
ACR-3.13

The system SHALL handle tool failures gracefully without exposing internal state or credentials in e

The system SHALL handle tool failures gracefully without exposing internal state or credentials in error responses.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3
ACR-3.14

The system SHALL detect and reject tool responses containing injection payloads or anomalous data pa

The system SHALL detect and reject tool responses containing injection payloads or anomalous data patterns.

AT+HS|Risk weight: 5/10|
L1L2L3
ACR-3.15

Tool access policies SHALL be versioned and changes require documented approval.

Tool access policies SHALL be versioned and changes require documented approval.

EIEvidence Inspection|Risk weight: 3/10|
L1L2L3
ACR-3.16

The system SHALL support tool access revocation that takes effect immediately upon authorization cha

The system SHALL support tool access revocation that takes effect immediately upon authorization change.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3
ACR-3.17

Tool invocations from different security contexts SHALL be isolated from each other.

Tool invocations from different security contexts SHALL be isolated from each other.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3
ACR-3.18

The system SHALL validate tool certificates and authentication tokens before each invocation.

The system SHALL validate tool certificates and authentication tokens before each invocation.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3
ACR-3.19

Tool invocation parameters SHALL be validated against expected types and ranges before transmission.

Tool invocation parameters SHALL be validated against expected types and ranges before transmission.

ATAutomated Testing|Risk weight: 3/10|
L1L2L3
ACR-3.20

The system SHALL detect and prevent data exfiltration through tool invocation parameters or payloads

The system SHALL detect and prevent data exfiltration through tool invocation parameters or payloads.

AT+HS|Risk weight: 5/10|
L1L2L3
ACR-3.21

Tool invocation results SHALL NOT be cached beyond defined freshness periods without revalidation.

Tool invocation results SHALL NOT be cached beyond defined freshness periods without revalidation.

ATAutomated Testing|Risk weight: 3/10|
L1L2L3
ACR-3.22

The system SHALL maintain separate tool authorization contexts for different operational modes (e.g.

The system SHALL maintain separate tool authorization contexts for different operational modes (e.g., production vs. testing).

AT+EI|Risk weight: 3/10|
L1L2L3
ACR-3.23

Tool dependencies SHALL be documented and monitored for availability, with fallback behavior defined

Tool dependencies SHALL be documented and monitored for availability, with fallback behavior defined for each.

EI+CM|Risk weight: 3/10|
L1L2L3
ACR-3.24

The system SHALL enforce mutual authentication with external tool providers where supported.

The system SHALL enforce mutual authentication with external tool providers where supported.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3
ACR-3.25

Tool access SHALL be automatically suspended when anomalous usage patterns exceed defined severity t

Tool access SHALL be automatically suspended when anomalous usage patterns exceed defined severity thresholds.

AT+CM|Risk weight: 4/10|
L1L2L3
ACR-3.26

The system SHALL log all tool authorization decisions including both grants and denials.

The system SHALL log all tool authorization decisions including both grants and denials.

ATAutomated Testing|Risk weight: 3/10|
L1L2L3
ACR-3.27

Tool invocations SHALL be identifiable and attributable to the originating decision context.

Tool invocations SHALL be identifiable and attributable to the originating decision context.

AT+EI|Risk weight: 4/10|
L1L2L3
ACR-3.28

The system SHALL prevent recursive tool invocations that could result in infinite loops or resource

The system SHALL prevent recursive tool invocations that could result in infinite loops or resource exhaustion.

ATAutomated Testing|Risk weight: 4/10|
L1L2L3