privacy-gateway-mcp
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| redact_previewA | Show what would be redacted and how the egress policy would rule — without sending anything or issuing an approval token. |
| ask_cloud_llmA | Send text to the cloud LLM through the privacy gateway. The text is redacted first; then the deterministic policy decides. Possible
|
| confirm_sendA | Approve and release a payload the policy flagged for human approval. The token is single-use and time-limited. |
| get_audit_logA | Return the append-only log of every egress decision made this session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| audit_log_resource | The audit trail as a readable JSON resource. |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: previewing redactions, confirming sends, auditing decisions, and making requests. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (redact_preview, confirm_send, get_audit_log, ask_cloud_llm), making them predictable and easy to use.
Four tools cover the essential workflow of a privacy gateway without unnecessary bloat or missing critical operations.
The set covers the full lifecycle: preview (redact_preview), action (ask_cloud_llm), approval (confirm_send), and audit (get_audit_log). No obvious gaps.