jevqueue
Related Servers
Alternatives to jevqueue
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents and MCP clients to route every tool call through configurable rules that allow, block, or hold risky actions for human approval, while recording decisions in a tamper-evident audit trail.12588 PyPI18Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides governed tools for evaluating proposed agent actions against policy, classifying risk, and creating structured governance and audit records, while pausing consequential steps for explicit human approval. This lets agentic workflows run under traceable, least-privilege control rather than unrestricted automation.MIT
- AlicenseNot gradedqualityBmaintenanceA local gate that lets agents submit risky tool actions for policy evaluation and receive ALLOW, DENY, or REQUIRE_APPROVE decisions before executing irreversible side effects. It can also open human approval holds and record an activity trail without executing the side effect itself.1,336 npm3MIT
- AlicenseAqualityBmaintenanceEnables agents to score, inspect, and gate tool calls before they execute, resolving shell commands the way a shell would in order to block destructive actions and detect multi-step attack sequences. It also redacts credentials and PII in either direction, requires signed single-use approval tokens for high-impact actions, and keeps a tamper-evident audit trail.611 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceA free, local check before your AI agent acts: every tool action is checked against your YAML rules and returns ACT, BLOCK or ESCALATE with an audit record. Optional: send escalations to Flow for a judgment.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.1MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of overlap or misselection between tools. Its stated purpose—querying a decision layer before a risky or redundant step—is clearly bounded and not duplicated elsewhere in the set.
The single name `jevqueue_decide` uses a predictable server-prefix + verb pattern that reads clearly. With only one tool there is no mixed convention, though also no broader pattern to confirm consistency across a set.
A one-tool surface is extremely thin for a server presented as a decision layer; the rubric treats a single tool as too few for the apparent scope. All decision functionality is crammed into one opaque call with no separate operations for outcome reporting, pending-step inspection, or configuration.
If the server is purely a read-only verdict oracle, one tool can cover its core purpose. However, there are notable gaps: no way to report whether a decision was correct, no listing of pending steps, and no batch or parameterized variants, making the lifecycle only partially closed.