enclave-gateway
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| enclave_statusB | Retrieve health telemetry for the Appliance VM, VPN tunnel, Bastion RDP VFS worker, and configured TargetNodes. |
| enclave_doctorB | Run L1-L7 diagnostics across Host, Appliance clock skew, RDP UDP blackhole guard, VPN tunnel, Bastion VFS RTT, and optional TargetNode SSH. |
| enclave_healB | Heal Appliance MTU (1350), disable RDP-over-UDP, optionally refresh interactive session credentials, and reconnect the Bastion RDP session. |
| enclave_cleanB | Purge transient spool chunks, staging files, and open multiplexed sockets across Appliance and Bastion. |
| node_execB | Execute a shell/PowerShell script on '@appliance', '@bastion', or a configured TargetNode with Base64 transport and secret scrubbing. |
| node_transferB | Push or pull a file between the Host and '@appliance', '@bastion', or a TargetNode with SHA-256 verification and optional block delta sync. |
| node_syncA | Synchronize a directory between the Host and a node; scoped grants commit each file atomically and retain extra destination files. |
| enclave_ssh_configA | Generate an OpenSSH ~/.ssh/config snippet using |
| node_db_queryC | Execute a SQL statement on a TargetNode (either directly on the host or inside a Docker container) without CLI password exposure. |
| node_http_requestC | Perform an HTTP/HTTPS request from inside a TargetNode to inspect internal services. |
| node_read_fileA | Read a UTF-8 file (or line range) from '@appliance', '@bastion', or a TargetNode with SHA-256 hash and secret scrubbing. |
| node_patch_fileB | Atomically replace a target block inside a remote UTF-8 file on '@appliance', '@bastion', or a TargetNode with optional SHA-256 precondition check. |
| enclave_tunnelB | Dynamically start, stop, or list background TCP port forwards or universal SOCKS5/HTTP proxies over RdpVfsTransport. |
| enclave_auditB | Retrieve recent session audit log entries from the FlightRecorder and verify its SHA-256 hash chain integrity. |
| enclave_transactionC | Get/list operation state and retained result, request cancellation, or mark expired execution indeterminate. Identity comes from the authenticated connection. |
| enclave_capabilitiesB | Report local capabilities and explicit unverified qualification boundaries without probing a live enclave. |
| enclave_agentB | Verify fresh running-worker evidence against pinned release hash, signer, OS account and execution model. |
| enclave_providerC | Plan/apply an administrator-approved, version-pinned provider lifecycle recipe. No inferred proprietary commands. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| enclave-diagnose | Run L1-L7 diagnostics and self-heal any enclave connectivity drift. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Enclave Topology | Configured Appliance, Bastion, TargetNodes, and PortForwards. |
| Enclave Health Telemetry | Live health status across Appliance, VPN, and Bastion. |
TDQS
Scored across 18 tools
Most tools map cleanly to a distinct resource+action (file read/patch, exec, transfer, sync, db_query, http_request, tunnel, audit, transaction). The main overlap is enclave_status vs enclave_doctor (both report health/diagnostics) and enclave_heal vs enclave_clean (both remediation), which could cause occasional misselection despite descriptions that differentiate them.
Strong two-prefix scheme (enclave_* for control-plane, node_* for remote operations) applied uniformly across all 18 tools. Minor deviation: node_* tools use clear verbs (read_file, exec, sync) while enclave_* tools mix nouns (status, tunnel, audit, capabilities) with verbs (heal, clean), so the action is not always evident from the name alone.
18 tools sits at the upper end of the comfortable range, but the domain is genuinely broad (appliance, VPN/bastion, target nodes, diagnostics, remediation, tunneling, SQL/HTTP probing). Each tool covers a distinct operational need rather than being redundant padding, so the count is defensible.
Covers the lifecycle well: status/doctor/heal/clean for health, read/patch/transfer/sync for files, exec/db_query/http_request for remote action, plus tunnel, audit, transaction, capabilities and ssh_config. Minor gaps: no explicit remote directory listing or file delete (workable via node_exec or node_sync), and no dedicated tunnel health/teardown verification beyond enclave_tunnel's list mode.