aletheia-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aletheia_set_mandateA | Establish or update the active operational safety mandate for this agent session. Declares permissible boundaries, allowed tools, filesystem directories, write permissions, and risk tolerance. Loosening restrictions requires operatorSecret. |
| aletheia_get_mandateA | Retrieve the current operational safety mandate, permissions, and active boundary constraints. |
| aletheia_interceptB | Universal sub-millisecond safety gatekeeper. Evaluates any proposed tool invocation against Signature S3 (Scope Creep) and S2b (Prompt Injection) to block destructive, out-of-boundary, or compromised actions before execution. |
| aletheia_safe_bashA | Execute a shell/bash command with inline sub-millisecond Signature S3 scope creep protection. Blocks destructive deletes (rm -rf), disk formatting, fork bombs, credential harvesting, privilege escalation, and unauthorized network egress. |
| aletheia_safe_sqlA | Audit or execute a database query with Signature S3 safety filters. Detects destructive DDL (DROP, TRUNCATE), unbounded DML (DELETE/UPDATE without WHERE), and privilege tampering. |
| aletheia_get_telemetryA | Retrieve runtime safety telemetry: total tool calls evaluated, block rate %, latency percentiles (p50, p95, p99 < 1ms), and violation counts broken down by signature. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| aletheia_mandate_enforcer | System prompt directive establishing operational safety boundaries, tool-use conservatism, and mandatory clearance through Aletheia. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Aletheia Runtime Telemetry Summary | Real-time statistics on intercepted tool calls, block rate %, and sub-millisecond latency distribution. |
| Aletheia Rolling Audit Log | Last 50 tool clearance requests with inputs, verdicts, violation signatures, and timestamps. |
| Signature S3: Scope Creep Beyond Mandate | Empirical specification, risk taxonomy, and failure rate data for Signature S3 from the Aletheia benchmark. |
| Active Operational Mandate | The active session mandate parameters, permitted tool boundaries, and permission toggles. |
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: mandate retrieval/update, telemetry, safe shell execution, safe SQL execution, and universal interception. Even though safe_bash and safe_sql both enforce safety, their execution targets are explicit and non-overlapping; intercept is described as evaluation-only, so an agent can tell them apart.
All tools share the aletheia_ prefix and snake_case, but the pattern is not uniform: get/set tools use verb_object, safe_bash/safe_sql use a modifier prefix, and intercept is a bare verb. This is readable and mostly predictable, with only minor deviations.
Six tools is well-scoped for a focused safety/governance MCP. Each tool addresses a distinct concern: mandate configuration, safe execution in two runtimes, telemetry, and universal interception, with no redundant extras.
The surface covers the core lifecycle: mandate get/set, safe execution, telemetry, and a universal gatekeeper. Minor gaps exist such as no dedicated safe file or HTTP action, but bash and SQL coverage plus intercept likely covers most operational needs.