Back
NOVA MCP // NOVA MCP Safety & Privacy
NOVA MCP Safety & Privacy
Docs › NOVA MCP
Safety & privacy
What NOVA MCP will and will not do.
Nothing live without youDeploys, rollbacks, environment changes and NOVA's fixes all need your yes.
Secrets stay secretEnvironment values are write-only, logs replace secrets with their names, and the scan shows keys masked.
Only your projectsA connection works on the projects you own. A project someone shared with you is not available through NOVA MCP, and NOVA says so; work on it in NOVA, or ask its owner. Any other account's project looks like it does not exist.
No browser sessionNOVA MCP only accepts its own sign-in or an API key, never your NOVA browser session, so no web page can drive it.
You can cut it offDisconnect a tool or revoke a key on the NOVA MCP page in your account; it stops at once.
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.