hejdar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEJDAR_API_KEY | Yes | Your Hejdar API key | |
| HEJDAR_API_URL | No | API base URL (for self-hosted) | https://api.hejdar.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hejdar_evaluateA | Evaluate an AI agent action against Hejdar security policies BEFORE executing it. Returns ALLOW, DENY, or WOULD_DENY. Call this before any sensitive action (read, write, delete, transfer, execute) to check if the action is permitted by organizational policy. If the decision is DENY, do NOT execute the action. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.