Vizier
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIZIER_API_KEY | No | Optional integration credential. Discovery requires no key. A key alone does not grant ALLOW; owner-signed delegation is a separate requirement. | |
| VIZIER_BASE_URL | Yes | Hosted Vizier origin; use https://vizier.agendamcp.dpdns.org for the maintained deployment. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Vizier is a deterministic authorization kernel. Call 'vizier_screen_action' before high-stakes operations (e.g. bash commands, file modifications, external writes, payments) to obtain cryptographic ALLOW/BLOCK receipts. Call 'vizier_verify_receipt' to validate proof of compliance. Call 'vizier_check_policy' to screen parameters or text for DLP secrets and sanctions.
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 |
|---|---|
| vizier_screen_actionA | Screen and authorize a proposed AI agent action before execution. Evaluates deterministic policy constraints, DLP leakage, loop prevention, and returns an ALLOW / REVIEW / BLOCK decision with an auditable cryptographic receipt. |
| vizier_verify_receiptB | Verify a cryptographic receipt or audit proof issued by Vizier. Validates token structure, expiration, and exact request/action hash binding. |
| vizier_check_policyA | Check content or parameters against security guardrails (DLP credential/PII leaks, sanctions screening, or circuit breaker loop limits). |
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 3 tools
verify_receipt is clearly distinct, but screen_action and check_policy overlap substantially: screen_action already evaluates DLP leakage, policy constraints, and loop prevention, while check_policy checks content/parameters against DLP, sanctions, and loop limits. The descriptions hint that one is a pre-execution authorization gate and the other a narrower guardrail check, but an agent could reasonably select either for the same content-screening need.
All three tools use the same vizier_ prefix followed by a clear verb_noun pattern: screen_action, verify_receipt, check_policy. The convention is predictable and readable throughout.
Three tools is reasonable for a focused runtime security/authorization layer, and each appears to serve a role. It sits at the low end of the typical 3-15 range, with little room for policy management or introspection.
The surface covers the core lifecycle: screen an action, check guardrails, and verify an issued receipt. Minor gaps exist around policy configuration/listing or retrieval of prior receipts, but the essential authorization and audit workflows are present.