-
Notifications
You must be signed in to change notification settings - Fork 0
feat: integrate OutputScanner into ToolInvoker execution flow #263
Copy link
Copy link
Closed
Labels
prio:highImportant, should be prioritizedImportant, should be prioritizedscope:smallLess than 1 day of workLess than 1 day of workspec:securityDESIGN_SPEC Section 12 - Security & Approval SystemDESIGN_SPEC Section 12 - Security & Approval Systemspec:toolsDESIGN_SPEC Section 11 - Tool & Capability SystemDESIGN_SPEC Section 11 - Tool & Capability Systemtype:featureNew feature implementationNew feature implementation
Description
Summary
OutputScanner exists as a standalone class (security/output_scanner.py) for post-tool output scanning and redaction. Per D5, it should be integrated into ToolInvoker to scan tool results after execution. This integration is not done.
Design Spec Reference
- §12.3 D5 — add post-tool-call scanning for sensitive data in outputs
Scope
- Wire
OutputScannerintoToolInvoker.invoke_all()post-execution path - Scan
ToolResult.contentfor sensitive data patterns - Redact or flag findings before returning results to the LLM
- Configurable per autonomy level
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
prio:highImportant, should be prioritizedImportant, should be prioritizedscope:smallLess than 1 day of workLess than 1 day of workspec:securityDESIGN_SPEC Section 12 - Security & Approval SystemDESIGN_SPEC Section 12 - Security & Approval Systemspec:toolsDESIGN_SPEC Section 11 - Tool & Capability SystemDESIGN_SPEC Section 11 - Tool & Capability Systemtype:featureNew feature implementationNew feature implementation