Skip to main content
Glama
jamjet-labs

jamjet-policy

Official
by jamjet-labs

Related Servers

Alternatives to jamjet-policy

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Runtime proxy that intercepts and blocks MCP tool calls based on YAML-defined policies, enforcing security rules for AI agents like Claude Code or Cursor.
      66 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables developers to wrap existing MCP servers with a deterministic policy enforcement gate that intercepts tool discovery and tools/call requests over stdio, allowing only authorized calls to reach the downstream server. It supports dynamic tool exposure or hiding, allow/deny/approval-required decisions, configurable error disclosure modes, and Ed25519-signed retry credentials for approved workflows.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Policy-enforcing MCP proxy that blocks dangerous tool calls before they execute. Protects credentials, filesystem, shell, and databases across Claude Desktop, Cursor, Windsurf, and OpenClaw.
      20 npm
      39
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Sits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Governs any stdio MCP server by interposing between the agent and the server, enforcing policy on every tools/call and refusing denied actions before they reach the upstream server.
      13 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides an MCP stdio interface for AI agents to propose tool calls that are validated against task policy, held for human approval when required, executed in a sandboxed Linux environment, and recorded in an audit log.
      MIT

    TDQS

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: evaluate a specific tool against policy, list all rules, and report loaded policy info. No overlap between them.

    Naming Consistency5/5

    All tools follow the consistent pattern 'policy_verb[_noun]' using snake_case, making them predictable and easy to understand.

    Tool Count5/5

    With 3 tools, the server is tightly scoped to policy inspection and evaluation, fitting its purpose well without unnecessary bloat.

    Completeness5/5

    The set covers the essential operations for a read-only policy server: evaluating a candidate, inspecting rules, and confirming the loaded policy. No missing functionality for its intended use.

    Maintenance

    ActivityStale
    ResponsivenessNo issues