Macuse: why it is not safe to use

What we found

Macuse (macuse-app/macuse-mcp) cleared our automated review with a score of 88/100. The MIT-licensed bundle contains no hardcoded secrets, no obfuscated or eval-style code, no destructive shell commands, and no remote script fetches at runtime. The wrapper itself makes no outbound network calls, and the vendor states that processing stays on the Mac with no content telemetry.

Three items drew a caution rather than a failure, all tied to how the tool works by design:

• It reads Mail, Messages, and Notes content into the model, so malicious text sitting in your inbox could try to steer the agent toward other apps.
• Its Universal Computer Use can drive any visible app, including password managers and banking, so it can reach credential screens.
• That same breadth is effectively wide local control, click and type anywhere, on your Mac.

Each is gated behind native macOS permission prompts and explicit per-app, per-client authorization you can revoke.

What to do instead

You can use Macuse, with care. Grant app access one at a time rather than all at once, keep sensitive apps (password managers, banking) unauthorized or set to re-confirm per action, and treat unexpected inbox instructions with suspicion. Review and revoke permissions periodically.