Skip to main content
Glama
stcmain

whats-allowed-mcp

by stcmain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to whats-allowed-mcp

No user-submitted related servers found.

    Related Servers

    • EnterpriseRBACLeastPrivilegePo

      alphaparkinc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables analysis of historical agent tool-call audit logs to detect over-permissioned wildcards, synthesize strict least-privilege JSON security boundary policies, and quantify attack surface and blast-radius reduction.
      8
      MIT

    • Aegis

      prince-rai88
      F
      license
      A
      quality
      B
      maintenance
      A blast-radius auditor for AI agents that computes combined effective permissions across all connected MCP tools, detects dangerous capability combinations deterministically, and provides a live risk graph and one-click policy fixes.
      4
      -

    • Enterprise Agentic RBAC/ABAC

      Alpha-Park
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables synthesizing tight JSON authorization policies from historical agent tool-call audit logs, flagging over-permissioned wildcard grants and quantifying how much the attack surface shrinks. It also validates individual actions against the resulting guardrails to block privilege escalation.
      7
      MIT

    • Laguarde

      FuturPanda
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to evaluate actions against team-defined policies, record decisions, and obtain human approvals for potentially risky operations.
      56 npm
      1
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool addresses a distinct aspect of permission configuration: overall summary, file sources, behavioral anomalies, and unattended execution pathways. There is no functional overlap between the four tools; their purposes are clearly separated and easy to distinguish.

    Naming Consistency5/5

    All four tool names follow the same snake_case convention and are descriptive noun phrases that clearly reflect their output (e.g., permission_sources, rule_findings). The naming is consistent across the entire set, with no mixed conventions or ambiguous verbs.

    Tool Count5/5

    With only four tools, the server is tightly focused on its purpose of analyzing permission configuration. Each tool covers a necessary dimension of the domain, and the count is well within the ideal range for a specialized MCP server.

    Completeness5/5

    The tool set provides comprehensive coverage for inspecting and understanding permission configuration: a starting summary, source file inventory, anomaly detection, and unattended execution risk. For its diagnostic scope, there are no obvious missing operations or dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources