privatevault-gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PV_API_KEY | No | API key sent as x-api-key to the enforcement server. Required unless the server runs with PV_ALLOW_NO_AUTH=1. | |
| PV_AGENT_ID | No | Identity recorded on every decision. Defaults to privatevault-gate-dev. | privatevault-gate-dev |
| PV_FAIL_OPEN | No | Set to '1' to allow actions when the engine is unreachable. Never set in production. Default: unset. | |
| PV_TIMEOUT_MS | No | Decision timeout in milliseconds before failing closed. Defaults to 5000. | |
| PV_ENFORCE_URL | No | Base URL of the enforcement API. Defaults to http://localhost:8000 | http://localhost:8000 |
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 |
|---|---|
| pv_execA | Run a shell command, gated by PrivateVault. Submitted for a pre-execution decision and only runs if the verdict is ALLOW. |
| pv_write_fileB | Write content to a file, gated by PrivateVault. Only happens if the verdict is ALLOW. |
| pv_http_requestA | Make an outbound HTTP request, gated by PrivateVault. Only sent if the verdict is ALLOW. |
| pv_decideA | Ask PrivateVault for a decision WITHOUT executing. Advisory only — nothing enforces that you honor the verdict, unlike the pv_* tools where execution is structurally behind the check. |
| pv_blockedA | List recent BLOCK decisions for this agent. |
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 5 tools
Each pv_* tool has a distinct purpose (exec, write, HTTP, decide, list blocked). Minimal ambiguity between pv_decide (advisory) and the gated tools is mitigated by clear descriptions of enforcement.
All tools use a consistent pv_ prefix with snake_case verbs. Minor deviation: 'decide' is an action but 'blocked' is a list operation, but the pattern is still predictable.
Five tools perfectly suit a security-gating server: core gated operations plus an advisory decision and a history check. No bloat or gap in scope.
The server covers the essential lifecycle of gating actions and checking decisions. Missing features like allowing/denying decisions or a detailed audit log, but these are secondary for advisory/lists.