canvas-mcp-developer

The server uses environment variables for sensitive Canvas API tokens and cookie paths, which is good practice. It also implements rate limiting to respect Canvas API limits. `child_process.spawn` is used for Python bridge scripts, which is safer than `exec`. However, the 'read-only access' claim in the README is contradicted by the presence of `canvas_bookmark_create` and `canvas_bookmark_delete` tools, which perform write operations (though minor, affecting only the user's bookmarks). The `notebooklm_prepare_content` tool takes user-provided `input_path` and `output_dir` which, in an adversarial AI scenario, could theoretically lead to path traversal for reading/writing arbitrary files on the server if not strictly contained. However, for its intended use case with a trusted AI agent, these are considered low risk.