feat(ai): Harden tool access exclusion across all providers
This commit is contained in:
@@ -1,8 +1,8 @@
|
||||
# Implementation Plan: Expanded Test Coverage and Stress Testing
|
||||
|
||||
## Phase 1: Tool Accessibility and State Unit Tests
|
||||
- [ ] Task: Review current tool registration and disabling logic in `src/mcp_client.py` and `src/api_hooks.py`.
|
||||
- [ ] Task: Write Tests: Create unit tests in `tests/test_agent_tools_wiring.py` (or similar) to verify turning a tool off removes it from the agent's available tool list.
|
||||
- [x] Task: Review current tool registration and disabling logic in `src/mcp_client.py` and `src/api_hooks.py`.
|
||||
- [~] Task: Write Tests: Create unit tests in `tests/test_agent_tools_wiring.py` (or similar) to verify turning a tool off removes it from the agent's available tool list.
|
||||
- [ ] Task: Implement: If tests fail due to missing logic, update the tool filtering implementation to ensure disabled tools are strictly excluded from the context sent to the provider.
|
||||
- [ ] Task: Conductor - User Manual Verification 'Phase 1: Tool Accessibility and State Unit Tests' (Protocol in workflow.md)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user