Proximo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXIMO_AUDIT_KEYED | No | Defaults to on; set to 'off' to disable HMAC-SHA256 keying of the audit ledger. | 1 |
| PROXIMO_ENABLE_EXEC | No | Opt-in: enables near-root LXC exec via SSH. Off by default. | 0 |
| PROXIMO_CT_ALLOWLIST | No | Comma-separated list of CTIDs allowed for exec (fail-closed). | |
| PROXIMO_ENABLE_AGENT | No | Opt-in: enables qemu-guest-agent operations inside VMs. Off by default. | 0 |
| PROXIMO_LEDGER_REDACT | No | If set to '1', record fingerprint instead of SQL body/command argv in ledger (privacy). | 0 |
| PROXIMO_A2A_TOKEN_FILE | No | Path to a file containing the bearer token for A2A server (non-localhost bind requires this). | |
| PROXIMO_AGENT_ALLOWLIST | No | Comma-separated list of VMIDs allowed for agent operations (fail-closed). | |
| PROXIMO_AUDIT_EXPECTED_HEAD | No | Expected head hash for audit verification (off-box anchor against tail truncation/forgery). |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_entriesA | READ-ONLY: WHO changed WHAT and WHEN — guest configuration changes and every other audited action, read back from the PROVE ledger. Newest first. This is how you answer "who changed this guest" or "what has this caller
done". |
| audit_verifyA | Verify the tamper-evident audit ledger's hash chain — PROVE the log is intact. Pass |
| proximo_callA | Call any Proximo tool by exact name, including ones not in this server's listed tools. Get the argument shape from proximo_tool_schema first. Same gates as calling it directly: dry-run PLAN, ledger entry, token ACL. A smaller doorway, not a looser one. |
| proximo_recallA | READ-ONLY: the estate map from local Tier-1 memory — NOT a live PVE read. Returns
total/by_kind/by_status/guest_summary counts (trust guest_summary for guest-count questions;
all counting is server-side) plus lean entity rows, stamped {source:'memory', as_of,
age_seconds}: the data is as old as the stamp says. With |
| proximo_find_toolsA | Search Proximo's full tool catalog by keyword. ESTATE QUESTIONS FIRST: if the question is what exists, how many, what changed, or when something last happened, call proximo_recall instead — it answers from local memory in one call, with no search and no schema lookup, and it stamps how old the answer is. Come here for everything else. The facade is resident; 924 more tools on this server are searchable but not. Search for what you want ("guest power", "ceph pool", "firewall"), then call proximo_tool_schema on a result to get its arguments, then proximo_read (read-only tools) or proximo_call to run it. All terms must match. |
| proximo_tool_schemaB | Full description + JSON input schema for one tool found via proximo_find_tools. |
| proximo_readA | READ-ONLY: run a read-only Proximo tool by exact name; refuses anything that can mutate (use proximo_call for those). Same flow: get the shape from proximo_tool_schema first. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| safe_migration | Runbook: migrate a guest to another node safely (plan-first, verify-after). |
| diagnose_cluster | Runbook: read-only health sweep of the cluster (DIAGNOSE, no changes). |
| provision_container | Runbook: provision a new LXC within policy (plan-first, verify-after). |
| safe_backup | Runbook: back up a guest and verify the backup actually landed. |
| review_receipts | Runbook: verify Proximo's PROVE ledger integrity (the receipts). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The set is largely distinct: audit_entries reads vs audit_verify proves the ledger, and proximo_find_tools carries explicit steering to prefer proximo_recall for estate questions. The main soft spot is proximo_call vs proximo_read, which overlap in purpose and rely on the mutating/read-only distinction in descriptions to separate them.
Names are snake_case throughout with clear domain prefixes (audit_* for ledger, proximo_* for the facade), which is readable and predictable. The verb/noun pattern varies a bit (find_tools, tool_schema, call, read are not uniform verb_noun), but no chaotic mixing.
Seven tools is well-scoped for a facade that fronts 900+ hidden tools, and each earns its place: discovery, schema lookup, two execution paths, memory recall, and audit read/verify. No bloat and no obvious redundancy in count.
The surface covers the full gateway lifecycle: find tools, get schema, execute (read or call), recall estate memory, and read/verify the audit ledger. Minor gap is no explicit list-all or paginated catalog browsing beyond keyword search, but agents can work around it.