Llm Guard Privacy Gateway

Created By
Amywith6 months ago
Overview

what is LLM-Guard Privacy Gateway?

LLM-Guard Privacy Gateway is a privacy protection gateway based on the MCP protocol, designed to detect and filter sensitive information in LLM applications.

how to use LLM-Guard Privacy Gateway?

To use LLM-Guard, install the required packages and utilize the provided functions to sanitize prompts by removing sensitive information. You can run it as an MCP tool server to ensure data privacy.

key features of LLM-Guard Privacy Gateway?

  • PII Redaction: Automatically identifies and replaces sensitive information such as names, phone numbers, and emails with placeholders.
  • Key Interception: Detects common API keys and sensitive credentials.
  • Commercial Blocking: Allows defining a blacklist of terms that, if found in the text, will trigger an interception.
  • MCP Packaging: Encapsulates the above logic into an MCP tool, returning results in JSON format.

use cases of LLM-Guard Privacy Gateway?

  1. Sanitizing user inputs in applications to prevent data leaks.
  2. Ensuring compliance with data protection regulations by filtering sensitive information.
  3. Integrating with LLM applications to enhance privacy and security.

FAQ from LLM-Guard Privacy Gateway?

  • Can LLM-Guard handle all types of sensitive information?

Yes! LLM-Guard is designed to detect various types of PII and sensitive data.

  • Is LLM-Guard easy to deploy?

Yes! It can be easily deployed using Docker or as a standalone service.

  • What happens if the required libraries are not installed?

The system has built-in error handling and will still function using default methods.

Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
Amywith
Star
-
Language
-
License
-
Category
security

Recommend Servers

View All
Payai X402 Tools

20 hours ago
Meteomatics

16 hours ago
GovQL
@Alex Stout

# govql-mcp-server An MCP (Model Context Protocol) server for [GovQL](https://govql.us) — gives AI clients like Claude Desktop, Claude Code, and Cursor direct access to the US Congressional GraphQL API at [api.govql.us/graphql](https://api.govql.us/graphql) without bespoke HTTP wiring. For the design rationale (why FastMCP-Python, the passthrough+curated philosophy, roadmap through v0.4), see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md). ## What you can do with it Ask an agent questions like: - *"How did Vermont's two senators vote on the most recent nomination?"* - *"Which legislators in the 118th Congress switched parties during their service?"* - *"Compare Senator Sanders' voting record to Senator Murkowski's on cloture votes in the most recent Congress."* The agent picks the right tool, writes the GraphQL query against the live schema, and parses the response — no manual API wrangling. ## Install The server runs as a per-client subprocess over stdio. Pick your client: ### Claude Desktop Edit `claude_desktop_config.json` (Settings → Developer → Edit Config): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` Restart Claude Desktop. The `govql` tools appear in the tools panel. ### Claude Code Add to `.mcp.json` in your project (or `~/.mcp.json` for global): ```json { "mcpServers": { "govql": { "command": "uvx", "args": ["govql-mcp-server"] } } } ``` ### Cursor Settings → MCP → Add Server. Use the same `command` / `args` as above. ### Other clients Any MCP-compatible client that supports stdio servers will work. The command is `uvx govql-mcp-server` with no required arguments. ## Tools | Tool | Purpose | |---|---| | `execute_graphql` | Run any GraphQL query against the GovQL endpoint. Returns the result plus an `last_ingest` timestamp so the agent can reason about data freshness. | | `list_types` | Returns the names and kinds of every type in the GovQL schema. Optional `kind` filter (`"OBJECT"`, `"INPUT_OBJECT"`, `"ENUM"`, etc.) to narrow further. Start here when you don't know what's queryable. | | `describe_type` | Returns one type's full details — fields, arg signatures, input fields, enum values. Call after `list_types` to learn the shape of a specific type before writing a query. | ## Configuration All env vars are optional — the package is zero-config for end users. | Env var | Default | Purpose | |---|---|---| | `GOVQL_ENDPOINT` | `https://api.govql.us/graphql` | Endpoint to query. Override to point at a local dev stack. | | `GOVQL_TIMEOUT_MS` | `30000` | Per-request HTTP timeout. | | `LOG_LEVEL` | `INFO` | Logging level. Logs go to stderr only (stdout is reserved for the MCP transport). | ## Limits (enforced by the upstream API) - Max query depth: 10 - Max query complexity: ~10 billion points (`first: N` multiplies child cost by N — keep page sizes reasonable on deeply nested queries) - Rate limit: 100 requests / 60 s per source IP A depth or complexity violation surfaces as a GraphQL `errors` entry in the tool response so the agent can adjust and retry. ## Data freshness Every `execute_graphql` response includes a `last_ingest` ISO timestamp. Vote data refreshes hourly; legislator data refreshes daily. ## Status Version 0.1.0 ships three foundational tools: a GraphQL passthrough (`execute_graphql`) and two narrow schema-discovery tools (`list_types`, `describe_type`). Curated higher-level tools (`find_legislator`, `get_voting_record`, `compare_voters`, etc.) are planned for subsequent releases — see [design.md](https://github.com/govql/govql/blob/main/mcp-server/docs/design.md) for the roadmap. ## Links - [GovQL project site](https://govql.us) - [GraphQL API](https://api.govql.us/graphql) - [Source / issues](https://github.com/govql/govql)

2 hours ago
Voyei

a day ago