lugh
Related Servers
Alternatives to lugh
- AlicenseNot gradedqualityBmaintenanceGives AI agents policy-checked tools for shell commands, file reads and writes, HTTP fetches and tool calls, deciding each action against a policy before it runs while tracking secret taint and recording every decision in a tamper-evident audit log.MIT
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents to request bounded GitHub changes through a default-deny policy, independent human approval, one-time execution with a GitHub App credential, and verifiable receipts.1-
- AlicenseNot gradedqualityCmaintenanceLocal-first AI agent for approval-gated automation and verifiable LLM workflows.1MIT
- AlicenseAqualityCmaintenanceLocal zero-trust permission gateway for AI agents. Enforces policy-based tool authorization, human approvals, scoped permissions, and cryptographically verifiable audit logs.4128 PyPI5Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI coding agents to access live operational context like processes, containers, and git state, while providing a tamper-evident audit log and policy-as-code compliance hooks locally.22445 npmBusiness Source 1.1
- FlicenseNot gradedqualityCmaintenanceEnables controlled AI-agent access to enterprise-shaped tools with a deny-by-default gated write path, human approval, dry-run execution, and append-only audit logging.1-

agentguardofficial
AlicenseNot gradedqualityAmaintenanceEnforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.MIT
TDQS
Scored across 5 tools
Each tool occupies a clearly distinct stage: reference (docs), check (compile only), run (execute goals in sandbox), test (execute test blocks), and sandbox (inspect the simulated world). The descriptions explicitly contrast check vs. run vs. test, so an agent can select without guessing.
All names share the consistent `lugh_` prefix with snake_case, giving a predictable namespace. Minor deviation: `reference` and `sandbox` are nouns while `check`, `run`, and `test` are verbs, so the verb_noun pattern isn't uniform.
Five tools map neatly onto the lifecycle of writing and validating a Lugh program: read docs, compile, run, test, inspect sandbox. Nothing feels padded or missing at this scope.
The surface covers the full authoring loop through simulated execution and policy logging, which is the stated purpose. Minor gaps: no lint/format or scaffolding tool, and no way to progress from sandbox to a real deployment, but agents can work around these via reference.