obsidian-mcp-bridge

The plugin allows user-defined JavaScript handler scripts loaded via `require()`. The documentation claims these scripts run in a 'restricted sandbox' that blocks file system access outside the vault, network requests, process spawning, and arbitrary module imports. The effectiveness of this sandboxing is critical for security, but its implementation details are not fully visible in the provided code snippets. The WebSocket server defaults to secure `127.0.0.1` (localhost) binding and requires an API key for authentication. Remote access is explicitly opt-in (`enableRemote` setting) and currently lacks SSL/TLS implementation, making remote connections over plain `ws` insecure. Users must trust the custom handler scripts they install and be aware of the implications of enabling remote access.