terraphim / terraphim/terraphim-ai
Phase 3: Implement Tool Management & Middleware
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 62
- Forks
- 5
- Avg merge
- 2h 27m
- Merged PRs (30d)
- 1
Description
Goal
Granular control and extensibility
Tasks
- Database table for tool status (ACTIVE/INACTIVE)
- Per-tool enable/disable in namespaces
- Tool override storage and application
- Tool discovery caching
- Define
McpMiddlewaretrait - Implement
FilterInactiveToolsMiddleware - Implement
ToolOverridesMiddleware - Add logging and error tracking middleware
- Create middleware composition pattern
- Error status enum for server states
- Structured logging for MCP operations
- Metrics collection (tool call latency, success rates)
- Health endpoint for monitoring
Success Criteria
- Can enable/disable individual tools within namespaces
- Middleware system is extensible
- Tool overrides work (rename/redescribe)
- Comprehensive observability
Timeline
Week 5-6
Depends on: Phase 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the completed Phase 2 work and the existing MCP server structure, then map each task to an implementation area. Done means individual namespace tool controls, extensible middleware and overrides, plus the listed logging, metrics, error-status, and health-monitoring capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, databases, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100