Skip to main content
Glama
AgentsID-dev

AgentsID Guard

Official
by AgentsID-dev

Related Servers

Alternatives to AgentsID Guard

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enforces deterministic policies for coding agents, inspecting file writes and shell commands to allow, deny, or require confirmation based on configurable rules.
      2 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      A Model Context Protocol (MCP) server that enables secure execution of shell commands with a dynamic approval system, audit logging, and command revocation.
      42
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enforces identity-based access control and audit logging for MCP servers, letting you grant fine-grained tool permissions to users and systems while failing secure by default.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.
      MIT

    TDQS

    A3.5/5.0

    Scored across 50 tools

    Disambiguation4/5

    Most tools are clearly separated by domain and action, but several run commands (shell, git, aws, kubectl, ssh) could be confused. Descriptions help by scoping each to a specific system, but the overlapping purpose makes misselection possible.

    Naming Consistency5/5

    All tool names are lowercase with underscores and consistently use a domain prefix plus a noun or verb (e.g., file_read, env_list, secrets_delete). The pattern is highly predictable and uniform across the set.

    Tool Count2/5

    With 50 tools, the server is heavy and covers many distinct subsystems. While each tool has a purpose, the count exceeds typical MCP server scopes and may overwhelm agents with too many options.

    Completeness4/5

    The tool set provides broad lifecycle coverage for secrets, files, processes, containers, and more. Minor gaps exist (e.g., no explicit update for cron jobs), but agents can work around them without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues