Tool and API Governance
Summary#
Tool invocation controls, permission scope, and API validation
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.
All tool invocations SHALL be authorized against a documented tool access policy.
All tool invocations SHALL be authorized against a documented tool access policy.
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.
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.
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.
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.
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.
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.
Tool output validation SHALL include schema validation, range checking, and format verification.
Tool output validation SHALL include schema validation, range checking, and format verification.
Tool output sanitization SHALL prevent injection attacks propagated through tool responses.
Tool output sanitization SHALL prevent injection attacks propagated through tool responses.
The system SHALL detect anomalous tool response sizes, latencies, and error rates.
The system SHALL detect anomalous tool response sizes, latencies, and error rates.
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.
Tool invocations SHALL include timeout mechanisms with defined maximum execution durations.
Tool invocations SHALL include timeout mechanisms with defined maximum execution durations.
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.
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.
Tool access policies SHALL be versioned and changes require documented approval.
Tool access policies SHALL be versioned and changes require documented approval.
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.
Tool invocations from different security contexts SHALL be isolated from each other.
Tool invocations from different security contexts SHALL be isolated from each other.
The system SHALL validate tool certificates and authentication tokens before each invocation.
The system SHALL validate tool certificates and authentication tokens before each invocation.
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.
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.
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.
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).
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.
The system SHALL enforce mutual authentication with external tool providers where supported.
The system SHALL enforce mutual authentication with external tool providers where supported.
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.
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.
Tool invocations SHALL be identifiable and attributable to the originating decision context.
Tool invocations SHALL be identifiable and attributable to the originating decision context.
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.