hejdar-mcp
Related Servers
Alternatives to hejdar-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnforces 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- AlicenseNot gradedqualityAmaintenanceDeterministic policy enforcement for AI agent tool calls. It evaluates every tool call against user-defined rules before execution, with no LLM in the authorization path.3MIT
- AlicenseNot gradedqualityBmaintenanceAn enforcement layer that validates AI agent actions against governance policies, including path permissions and content scanning, at runtime. It enables secure, role-based execution of file operations and commands with zero token overhead by processing policies independently from the agent's context.32 npm3MIT
- AlicenseAqualityAmaintenancePolicy-based governance for AI agent tool calls. YAML policies, approval gates, risk assessment, and audit logging across LangChain, OpenAI, Anthropic, and MCP.551 PyPI15MIT

Vaikora Guard MCPofficial
AlicenseNot gradedqualityDmaintenanceEnforces deterministic policies on AI agent tool calls, evaluating actions against compliance modules (SOC 2, HIPAA, GDPR, etc.) and returning ALLOW, BLOCK, or CONSTRAIN decisions with an audit trail.MIT- FlicenseAqualityFmaintenanceProvides policy-based access control, incident tracking, and compliance monitoring to govern AI agent behavior. It enables organizations to enforce security rules and maintain audit trails by validating agent actions against trust levels and pattern-based policies.61-
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined as evaluating AI agent actions against security policies, making it distinct and unambiguous in isolation.
A single tool inherently has perfect naming consistency since there are no other tools to compare against. The name 'hejdar_evaluate' follows a clear pattern of server prefix and action, which would be consistent if more tools existed.
A single tool is too few for a server that claims to handle security policy evaluation across various actions (read, write, delete, transfer, execute). This minimal set forces agents to rely solely on this one tool without dedicated tools for different policy aspects or actions, making the scope feel incomplete and thin.
The server's domain appears to be security policy evaluation for AI actions, but with only one tool, there are significant gaps. It lacks tools for managing policies, querying specific rules, or handling different types of security checks, which limits agents to a single evaluation call without supporting operations for a comprehensive workflow.