Skip to main content
Glama

Related Servers

Alternatives to aw1-circuit-breaker

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A universal interceptor that sits between any AI model's tool calls and shell execution, routing them through a supervisor daemon that inspects AST deltas, subprocess output, and hash-chained ledgers before work is allowed. It enables users to kill deleted assertions, trivial stubs, phantom test runs, and cyclic self-debate loops deterministically at the compiler, process, and filesystem boundaries rather than via prompt instructions.
      AGPL 3.0
    • A
      license
      A
      quality
      D
      maintenance
      Static worst-case token-budget analysis for LLM-agent workflows using AST analysis to identify certifiable, default-dependent, non-certifiable, and runaway units, with optional signed budget certificates.
      4
      30 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables autonomous AI agents and MCP clients to route tool calls through a zero-trust firewall that blocks dangerous shell commands, redacts secrets and PII, restricts sensitive file access, and logs verdicts. It provides an MCP interceptor decorator to protect MCP server tools with AST-based command injection checks and allow, block, or redact decisions.
      2
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to run shell commands, perform sandboxed file operations, and make HTTP requests through zero-trust guards that block command injection, path traversal, and SSRF while redacting secrets from inputs and outputs. Circuit breakers, per-session rate limits, and an append-only audit ledger prevent runaway loops, excessive token spend, and provide post-hoc traceability.
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools target clearly distinct objects: Python source code, external tool arguments, and containment-rule status. An agent can readily distinguish when to inspect code versus arguments versus check status.

    Naming Consistency5/5

    All names use consistent snake_case with a verb_noun pattern: inspect_python_code, inspect_tool_arguments, get_containment_status. The mix of inspect_* and get_* is predictable and semantically appropriate.

    Tool Count4/5

    Three tools is a focused, reasonable surface for a circuit-breaker-style security server. It is slightly thin, but each tool has a clear role and no obvious redundancy.

    Completeness3/5

    The server covers inspection and status reporting, but it lacks operations to configure, update, or reset the zero-trust containment rules. This is a notable gap if the server is meant to manage containment policy rather than only observe it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues