triliumnext-mcp

The server employs Zod for robust runtime input validation across all tool parameters, which is a strong security measure against common injection attacks. Permission checks are granular for READ/WRITE operations. Update operations require an `expectedHash` to prevent concurrent modification conflicts, enhancing data integrity. Past challenges with file/image uploads led to their temporary disablement, which mitigates potential path traversal or arbitrary file access risks associated with `fileUri` handling. Re-enabling file uploads would require extremely rigorous path validation. The primary remaining risk is the `TRILIUM_API_TOKEN`, which grants full access to the TriliumNext instance; it must be securely managed in the environment.