# Security and privacy

## Scope and permissions

This UI lists the current Harness plugin inventory through the existing Host transport and asks Plugin Manager to persist enable/disable changes for MCP plugin entries. It does not implement its own file writer, MCP client, credential store, analytics, or outbound HTTP client.

Enabling an entry can execute the MCP server command configured by the user. Disabling one may interrupt tools in other sessions in the same profile. Review your own server configuration before enabling it. An enabled switch is not a connection-health guarantee.

The plugin relies on Harness authorization and its existing Plugin Manager API. Installing this UI does not introduce a separate security boundary or limit what an already-authorized Host can do.

## What is not distributed

The repository does not need your Harness profile, actual MCP server list, environment variables, tokens, account email, local filesystem paths, logs, screenshots, or saved switch states. Its `cordis.patch.yml` inserts only the UI plugin; it is not a copy of a user's profile patch.

The runtime inventory is read from your own Host, not from this repository. Local UI error text and read-only explanations can include Host-provided details. Sanitize screenshots, logs, and reports before sharing them.

## Reporting a vulnerability

If available, use the repository's **Security → Report a vulnerability** private reporting feature. Availability depends on repository settings; this document does not imply that private reporting is enabled.

If private reporting is unavailable, open an issue asking the maintainer to arrange a private channel **without including exploit details, credentials, private configuration, or logs**. Do not publish sensitive details in an ordinary issue.

Only the current repository version is maintained. There is no guaranteed response time or security service-level agreement.

## Contributor checklist

- Do not commit real profile patches, server commands/configuration, `.env` files, credentials, local logs, or screenshots of private setups.
- Use GitHub's noreply commit address if you do not want a personal email exposed. Both author and committer metadata are public after pushing.
- Review staged files, the complete commit, Git history, and the actual package file list before pushing.
- Keep install hooks and dependencies absent unless separately reviewed.
- Run `npm test`. Static checks reduce mistakes but do not prove the absence of every possible secret or vulnerability.
- If a credential is ever pushed, revoke or rotate it immediately. Removing it in a later commit does not remove it from Git history or existing copies.