Datto BCDR

It requires DATTO_BCDR_PUBLIC_KEY, DATTO_BCDR_PRIVATE_KEY, region, and related environment variables; the private key is clearly a sensitive credential, and leakage could enable unauthorized access to the Datto BCDR account/API. The material does not show abnormal overreach, but normal credential-handling and least-privilege concerns apply.

No explicit remote host is provided, but given its Datto BCDR functions around appliances, agents, recovery points, and alerts, it is reasonable to infer communication with Datto-related services/APIs and transmission of query data. Endpoint and data-flow details are missing, so network egress is likely, but there is no evidence here of exfiltration to unknown or unrelated third parties.

The system flags it as executes-code, indicating the normal local runtime/process execution capability of an MCP tool. The provided material does not show system privileges beyond the stated purpose, nor suspicious command injection or persistence behavior, so this is caution rather than risk.

By description, it can access Datto BCDR appliances, agents, recovery points, screenshots, and alerts, which may include business-sensitive backup status, device information, alerts, and recovery metadata. The material does not indicate local file read/write or access scopes unrelated to its purpose, so there is no clear sign of overbroad access.

The source is an official registry entry and has an auditable open-source repository with updates within the last year, all of which are positive signals. Although the README is absent, the license is not declared, and community stars are very low, the current material does not show closed-source exfiltration, an unknown publisher, or other clear supply-chain red flags.