100% Open Source, Docker-First MCP Security Gateway that analyzes MCP tool calls for threats in real-time using pattern detection and semantic analysis. Provides threat scoring, session tracking, and multi-target attack orchestration detection.
Critical gaps across all dimensions. Tool definitions are inferred from example wrappers (TypeScript/JavaScript files in examples/) rather than visible in the Rust gateway codebase. No explicit tool registration, schemas, or descriptions found in the actual MCP server implementation (crates/gateway, crates/threat-engine). The threat-engine crate references 'tool_call.rs' but the actual tool definitions are not visible in provided source. Tool descriptions are generic placeholders ('protected by Proxilion') with no actionable guidance. Input schemas are minimal (only parameter names and types, no constraints, enums, or validation rules). No output schemas documented. Error handling is absent from visible code. This server appears to be a security gateway wrapper around tools rather than a fully-specified MCP server with proper tool definitions.
Execute a bash command (protected by Proxilion)
List contents of a directory (protected by Proxilion security)
Read contents of a file (protected by Proxilion)
Execute a terminal command (protected by Proxilion security)
Write contents to a file (protected by Proxilion)
Tool definitions inferred from example wrappers, not visible in gateway implementation. No explicit tool registration in crates/gateway or crates/threat-engine source code provided.
All tool descriptions are generic placeholders ('protected by Proxilion') under 20 characters. No actionable guidance on when/why to use each tool or what it returns.
Input schemas lack constraints, enums, validation rules, and output schemas are completely undocumented. No pagination support visible for list_directory despite returning potentially large results.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | <=2025-11-25 | v2 |
Irreversible operations (bash, run_terminal_command) lack dry-run, confirmation, or recovery guidance. No error handling visible to guide LLM on retryability or next steps.
Parameter descriptions missing for all tools. 'command' and 'path' parameters have minimal descriptions; no guidance on format, constraints, or examples.