Veil
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VEIL_UI_HOST | No | Secure UI bind address. | 127.0.0.1 |
| VEIL_UI_PORT | No | Secure UI bind port. | ephemeral |
| VEIL_OPEN_BROWSER | No | Open the authorization window automatically. | true |
| VEIL_ENABLED_ADAPTERS | No | Comma-separated allowlist of adapters. | all |
| VEIL_ENV_ALLOWED_ROOTS | Yes | Roots the `.env` adapter may write inside. Must be set to an absolute path. | |
| VEIL_STAGE_B_FOR_MEDIUM | No | Require confirmation for medium-risk operations. | true |
| VEIL_REQUEST_TTL_SECONDS | No | Request expiry in seconds. | 300 |
| VEIL_ALLOW_GIT_TRACKED_ENV | No | Permit writing into a git-tracked env file. | false |
| VEIL_ADAPTER_TIMEOUT_SECONDS | No | Upper bound on one destination write. | 30 |
| VEIL_DISCLOSE_AUTHORIZATION_URL | No | Return the authorization link to the agent. | false |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| secret.storeA | Ask the human to provide a credential and have Veil write it to the destination described here. The credential value is never passed through this tool, never returned by it, and never becomes visible to the model: the user enters it in Veil's own trusted window. Share the returned authorization_url with the user, then poll secret.status. |
| secret.statusA | Return the non-sensitive status of a credential request. Never returns credential material. |
| secret.cancelA | Cancel a pending request. Any credential already entered is destroyed. |
| secret.reviseA | Cancel a pending request and create a new one. The original authorization is invalidated and the human must authorize the new operation from scratch; an authorized operation can never be edited in place. |
| secret.destinationsA | List the destinations this Veil instance can write to, with the target fields each one expects. |
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 tool has a clearly distinct role: status checks a pending request, store initiates a credential request, cancel aborts it, revise replaces it, and destinations lists available targets. No overlap in purpose, making agent selection unambiguous.
All tool names follow a consistent 'secret.<action>' pattern with clear, concise verbs (status, store, cancel, revise) and one noun (destinations). The pattern is uniform and predictable, though 'destinations' is a noun rather than a verb, it still fits the domain prefix style.
With 5 tools, the server is tightly scoped to credential request management. This is within the ideal range and each tool earns its place; no redundancy or bloat.
The tool surface covers the entire lifecycle of a credential request: create (store), read (status), update/replace (revise), delete (cancel), and context (destinations). There are no evident gaps—even revision gracefully handles invalidation of prior authorizations.