llm-multiverse/llm-multiverse
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

feat: implement ValidateCall gRPC endpoint (#65) #163

Merged
shahondin1624 merged 1 commits from feature/issue-65-validate-call-endpoint into main 2026-03-10 16:47:56 +01:00
Conversation 0 Commits 1 Files Changed 3 +181 -9
shahondin1624 commented 2026-03-10 16:47:50 +01:00
Owner
Copy Link

Summary

  • Implement ValidateCall dry-run endpoint that runs the 5-layer enforcement pipeline without executing the tool
  • Reuses existing enforce() method by constructing an ExecuteToolRequest from ValidateCallRequest
  • Returns is_allowed, denial_reason, and enforcement_layer
  • 6 new tests covering allowed, denied, path checks, no side effects, and unknown agent type

Test plan

  • All 165 tool-broker tests pass
  • Clippy clean with -D warnings
  • Validates no side effects (10 repeated calls don't trigger loop detector)

Closes #65

## Summary - Implement ValidateCall dry-run endpoint that runs the 5-layer enforcement pipeline without executing the tool - Reuses existing `enforce()` method by constructing an ExecuteToolRequest from ValidateCallRequest - Returns is_allowed, denial_reason, and enforcement_layer - 6 new tests covering allowed, denied, path checks, no side effects, and unknown agent type ## Test plan - [x] All 165 tool-broker tests pass - [x] Clippy clean with `-D warnings` - [x] Validates no side effects (10 repeated calls don't trigger loop detector) Closes #65
shahondin1624 added 1 commit 2026-03-10 16:47:51 +01:00
feat: implement ValidateCall gRPC endpoint (issue #65) e9cb88eb28 
Wire the ValidateCall dry-run endpoint that runs the 5-layer
enforcement pipeline without executing the tool. Reuses the
existing enforce() method by constructing an ExecuteToolRequest
from the ValidateCallRequest. Returns is_allowed, denial_reason,
and enforcement_layer. 6 new tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
shahondin1624 merged commit 8965e849ae into main 2026-03-10 16:47:56 +01:00
shahondin1624 deleted branch feature/issue-65-validate-call-endpoint 2026-03-10 16:47:56 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
cat:agent
Agent related
 cat:cross-cutting
Cross-cutting concern
 cat:deployment
Deployment related
 cat:devops
DevOps related
 cat:performance
Performance related
 cat:security
Security related
 cat:tech-debt
Technical debt from code reviews
 lang:protobuf
Protocol Buffers
 lang:python
Python language
 lang:rust
Rust language
 priority:critical
Critical priority
 priority:high
High priority
 priority:low
Low priority
 priority:medium
Medium priority
 service:audit
Audit service
 service:memory
Memory service
 service:model-gateway
Model Gateway service
 service:orchestrator
Orchestrator service
 service:search
Search service
 service:secrets
Secrets service
 service:tool-broker
Tool Broker service
 type:bug
Bug fix
 type:documentation
Docs
 type:feature
New functionality
 type:infrastructure
Build tooling, project setup
 type:refactor
Restructuring
 type:research
Investigation, benchmarking
 type:testing
Tests
 workflow:blocked
Blocked after max retries
 workflow:manual
Requires manual intervention — blocked from auto-dev
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shahondin1624
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: llm-multiverse/llm-multiverse#163
Delete Branch "feature/issue-65-validate-call-endpoint"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?