humane-proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PATH | No | Environment path to ensure the humane-proxy CLI is executable | /app/.venv/bin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin |
| GROQ_API_KEY | No | Groq API Key for Stage 3 Reasoning (LlamaGuard) | |
| OPENAI_API_KEY | No | OpenAI API Key for Stage 3 Reasoning (OpenAI Moderation or Chat) | |
| HUMANE_PROXY_PORT | No | Proxy port | 8000 |
| HUMANE_PROXY_ADMIN_KEY | No | Bearer token for securing the /admin endpoints | |
| HUMANE_PROXY_ENABLED_STAGES | No | Active stages as a JSON array string (e.g., '[1, 2, 3]') | [1] |
| HUMANE_PROXY_RISK_THRESHOLD | No | Score threshold for criminal_intent escalation | 0.7 |
| HUMANE_PROXY_STAGE1_CEILING | No | Early exit after Stage 1 if score is below this threshold | 0.3 |
| HUMANE_PROXY_STAGE2_CEILING | No | Early exit after Stage 2 if score is below this threshold | 0.4 |
| HUMANE_PROXY_STAGE3_TIMEOUT | No | Stage 3 timeout in seconds | 10 |
| HUMANE_PROXY_STAGE3_PROVIDER | No | Stage 3 provider (auto, openai_moderation, llamaguard, openai_chat, none) | auto |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_message_safetyB | Classify a message for self-harm or criminal intent. |
| get_session_riskB | Return the current risk trajectory for a session. |
| list_recent_escalationsB | Return recent escalation events from the audit log. |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: check_message_safety analyzes individual messages, get_session_risk assesses ongoing session risk, and list_recent_escalations retrieves historical audit data. The descriptions clearly differentiate between real-time classification, session-level monitoring, and historical event logging.
All tools follow a consistent verb_noun pattern with clear, descriptive names: check_message_safety, get_session_risk, and list_recent_escalations. The naming convention is uniform throughout, using snake_case and action-oriented verbs that accurately reflect each tool's function.
Three tools is reasonable for a safety/risk monitoring server, covering key areas: message analysis, session tracking, and audit review. While slightly minimal, each tool serves a distinct and necessary function without redundancy. A few additional tools (e.g., for configuration or detailed event analysis) could enhance completeness but aren't essential.
The tools provide solid coverage for safety and risk monitoring: check_message_safety handles input classification, get_session_risk tracks ongoing risk, and list_recent_escalations offers historical context. Minor gaps include lack of tools for managing safety settings or escalating sessions, but agents can work effectively with the provided surface for core monitoring tasks.