ClawHub
Back to skill

Security audit

m365-mcp

Security checks across malware telemetry and agentic risk

Overview

This Microsoft 365 connector is transparent about its access and token storage, but users should treat the local OAuth tokens as sensitive secrets.

Install only if you are comfortable granting delegated Microsoft 365 access to the configured app. Prefer M365_MCP_READ_ONLY=true unless you need write actions, require confirmation for mutating tools in your MCP client, protect the auth directory, and revoke Microsoft account consent if the device or token files may be exposed.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Credential Access

High
Category
Privilege Escalation
Content
- Set `M365_MCP_READ_ONLY=true` for an enforced least-privilege mode. It requests
  read-only OAuth scopes, omits mutating tools from discovery, and rejects direct
  calls to them.
- Refresh and access tokens are stored as plaintext JSON under
  `~/.m365-mcp/auth/` (or `M365_MCP_AUTH_DIR`), protected with directory mode
  `0700` and file mode `0600` where supported. Protect that directory and revoke
  the app's Microsoft account consent if a token or device is compromised.
Confidence
95% confidence
Finding
access tokens

VirusTotal

62/62 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.