hitl-gate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HITL_ELICIT | No | 是否使用 Cursor 内审批表单 | 1 |
| HITL_DATA_DIR | No | 审批数据目录（建议绝对路径） | ./data |
| HITL_PANEL_PORT | No | 面板端口（仅开启面板时） | 8787 |
| HITL_ENABLE_PANEL | No | 是否启用本机网页备用面板 | 0 |
| HITL_OPEN_BROWSER | No | 面板启动时是否自动打开浏览器 | 0 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| assess_and_gateA | BUILTIN POLICY: Assess risk; if dangerous, create a ticket and request approval via Cursor in-IDE form (MCP elicitation). Returns approved/rejected when user decides in Cursor. Fallback: pending + chat/panel instructions. Call BEFORE side effects. Do NOT execute while pending/rejected. |
| list_dangerous_opsB | List the built-in dangerous operation catalog used by assess_and_gate (MCP-embedded policy). |
| request_approvalA | Manually request human approval (skip assessment). Uses Cursor elicitation when available. Prefer assess_and_gate for normal flow. |
| get_approval_statusA | Get approval ticket status. Only proceed when status is approved. Stop when rejected or expired. |
| list_pendingB | List all pending approval tickets waiting for human decision. |
| list_approval_historyA | List approval audit history for the user. Call when the user asks to 看审批记录 / view approval history / audit log. Present summary_zh in chat. Optional status filter and limit. |
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 6 tools
Each tool has a distinct purpose: assess_and_gate is the main gating action, get_approval_status checks a specific ticket, list_approval_history provides audit history, list_dangerous_ops catalogs risky operations, list_pending shows pending tickets, and request_approval allows manual bypass. No two tools have ambiguous overlap.
All tool names follow a consistent verb_noun pattern (e.g., list_pending, request_approval). The slight deviation in 'assess_and_gate' is minor and still clear.
With 6 tools, the server covers the essential operations for human-in-the-loop gating without being excessive or sparse. Each tool handles a specific, necessary function.
The tool set covers the full lifecycle: assessment (assess_and_gate), manual request (request_approval), status checking (get_approval_status), pending list (list_pending), history (list_approval_history), and catalog (list_dangerous_ops). No obvious gaps for the stated purpose.