Skip to main content

OneWolf MCP Server

OneWolf AI Security tools exposed via the Model Context Protocol.

Provides 6 security tools and 2 resources to MCP-compatible clients (Cursor, Claude Desktop, MCP Inspector, custom agents).

Tools

Tool Category Purpose
analyze_prompt text Detect prompt injection, jailbreak, PII, toxic content, secrets
filter_output text Sanitize LLM responses (mask PII, redact credentials, filter toxicity)
scan_document document Scan files for threats, PII, malicious content (Fenrir Shield)
rag_pre_check rag Validate user query before vector retrieval (exfiltration/injection)
rag_post_check rag Sanitize retrieved documents before LLM context
rag_ingest_check rag Analyze documents before knowledge-base ingestion (anti-poisoning)

Resources

URI Returns
guard://health API health status (filtered — no internal topology)
guard://capabilities Available tools and resources

Installation

pip install -e .

Or for development:

pip install -e ".[dev]"

Python 3.10+ required.

Configuration

Set these environment variables in your MCP client config:

Variable Required Default Description
ONEWOLF_API_KEY yes — Your OneWolf API key
ONEWOLF_URL no http://localhost:8001 Backend API URL
ONEWOLF_TIMEOUT no 30 Request timeout in seconds (text/RAG). Document scan uses 60s.

Setup — Cursor

Edit .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "onewolf-guard": {
      "command": "python",
      "args": ["-m", "onewolf_mcp"],
      "env": {
        "ONEWOLF_API_KEY": "your-api-key",
        "ONEWOLF_URL": "http://localhost:8001"
      }
    }
  }
}

Restart Cursor or toggle the server off/on in Settings → MCP. You should see "6 tools, 2 resources enabled".

Setup — Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "onewolf-guard": {
      "command": "python",
      "args": ["-m", "onewolf_mcp"],
      "env": {
        "ONEWOLF_API_KEY": "your-api-key",
        "ONEWOLF_URL": "http://localhost:8001"
      }
    }
  }
}

Restart Claude Desktop.

Setup — MCP Inspector (testing)

npx @modelcontextprotocol/inspector python -m onewolf_mcp

Set environment variables in the Inspector UI before connecting.

Limits and timeouts

  • Text input (analyze_prompt, filter_output, rag_pre_check): max 10,000 chars
  • Document size (scan_document, rag_ingest_check): max 50 MB (decoded base64)
  • RAG docs (rag_post_check): max 50 documents per call
  • Timeout (text/RAG): 30s default (ONEWOLF_TIMEOUT)
  • Timeout (document scan): 60s

Error handling

All tools return JSON. On failure, the response has an error field:

error Meaning
invalid_input Bad arguments (empty, oversized, invalid base64)
invalid_response API returned malformed response (fail-closed)
connection_failed Backend unreachable — check ONEWOLF_URL
timeout Backend did not respond in time
request_failed Generic HTTP error
api_error API returned 4xx/5xx (auth, rate limit, etc.)

Latency baseline

Measured against a healthy local backend (n=20 per tool, all values in ms):

Tool Cold (1st call) Warm p50 Warm p95
analyze_prompt 1040 49 54
filter_output 48 44 48
scan_document 1265 52 68
rag_pre_check 431 53 68
rag_post_check 423 54 62
rag_ingest_check 91 56 72

Mean warm p50: 51ms — Mean warm p95: 62ms

Cold-call latency is dominated by backend cache miss + ML model warmup (Cerberus/Fenrir). Warm latency reflects steady-state performance with backend caches warm.

Note: a true cold-start of the entire backend stack (Docker container boot + ML model load) takes ~18-30s and is not captured here.

See tests/baseline_latency.py for the benchmark script.

Testing

pytest tests/

69 tests covering: input validation, fail-closed behavior, API error mapping, contract alignment with backend (route names, field names), and a stdio smoke that drives the server as a real subprocess over the MCP protocol.

License

MIT

Metadata

Release files for onewolf-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for onewolf-mcp 0.2.0
File Size Uploaded Provenance Actions
onewolf_mcp-0.2.0.tar.gz 16.0 kB With provenance Details for onewolf_mcp-0.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for onewolf-mcp 0.2.0
File Interpreter ABI Platform Actions
onewolf_mcp-0.2.0-py3-none-any.whl Python 3 none any Details for onewolf_mcp-0.2.0-py3-none-any.whl

Total release size: 24.9 kB

Release files / onewolf_mcp-0.2.0.tar.gz

Download URL onewolf_mcp-0.2.0.tar.gz
Size 16.0 kB
Tags Source
SHA-256 checksum
How to use checksums
d89dd6c81fd7f46d56baa437bdae22d22dc08e6c6b558f41e1739e56b935ad80
BLAKE2b-256 checksum
How to use checksums
2cbdb6ac7ba48e8390a14abc459637bef1e4599800ea451f14df49e5907ac75e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Release files / onewolf_mcp-0.2.0-py3-none-any.whl

Download URL onewolf_mcp-0.2.0-py3-none-any.whl
Size 8.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
29c2128290f5baae8512bbae2d0f88a60ae71e66c60b47bb5fbfacd6c151aad7
BLAKE2b-256 checksum
How to use checksums
7314f882fdfa267889b0520875ab08177aceb68870d8c461e852ae3cb1484f67
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for onewolf-mcp 0.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for onewolf_mcp-0.2.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page