MCP-Open-Discovery-with-AMQP

The project implements robust security controls for its dynamic plugin architecture, including manifest validation, SHA256 integrity checks of plugin distributions, optional digital signature verification using trusted keys, and configurable dependency policies (e.g., 'bundled-only', 'sandbox-required'). A runtime sandboxing mechanism intercepts core Node.js module imports and external dependencies during plugin loading, enforcing permissions and detecting dynamic code execution (`eval`, `new Function`). Command injection risks for external tools (Nmap, network tools) are mitigated by critical input sanitization functions. Secrets are managed securely using environment variables or an encrypted local store with key rotation. OAuth 2.1 middleware is implemented for API protection, including token introspection and scope validation. A potential risk for default configurations is the 'allow-all' CORS policy for HTTP, which should be restricted in production, and Nmap tools requiring 'privileged' container capabilities.