Skip to content

Security: websec/ROADtools-MCP

Security

SECURITY.md

Security & Responsible Use

Authorized use only

roadtools-mcp reads from - and (via the collection and roadtx tools) authenticates to - live Entra ID / Azure / Microsoft 365 tenants. Only use it against tenants you own or are explicitly authorized in writing to assess (e.g. a signed penetration-test engagement). Unauthorized access to computer systems is illegal in most jurisdictions.

Handling of secrets and tenant data

  • Authentication tokens are written by ROADtools to .roadtools_auth inside each engagement folder (ROADTOOLS_WORKDIR, default ~/roadtools-engagements). These files contain live refresh tokens - treat them as credentials.
  • Collected databases (roadrecon.db) and exports contain sensitive tenant data.
  • The provided .gitignore excludes tokens, databases, logs and engagement folders so they are not committed. Do not override this.
  • Use cleanup_engagement (or delete the engagement folder) when you are done, and revoke the session/refresh tokens tenant-side.
  • This server never sends tenant data anywhere except back to the MCP client you connected; it talks only to your local ROADrecon GUI/database and to Microsoft during authentication.

Reporting a vulnerability

Please report security issues privately to the maintainer at joel@websec.nl rather than opening a public issue. We will acknowledge and work on a fix promptly.

There aren't any published security advisories