Schema | privacy-gateway-mcp

privacy-gateway-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

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`	{}

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 `status` values: `sent` (redacted text was dispatched and the reply re-hydrated), `blocked` (a hard rule refused it), or `needs_approval` (call `confirm_send` with the returned `confirmation_token`).
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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
`audit_log_resource`	The audit trail as a readable JSON resource.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jogustainsson/privacy-gateway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server