sysadmin
0a61e8a92d
Co-authored-by: Jason Walker <913443@dadeschools.net> Co-committed-by: Jason Walker <913443@dadeschools.net>
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
# MCP Safety Model
|
|
|
|
This document outlines the safety requirements for all tools within the MCP monorepo.
|
|
|
|
## 1. Audit Logging and Confirmation
|
|
All mutating actions (e.g., triggering builds, creating resources, updating environments) must be recorded in an audit log. These actions require explicit confirmation from the user before execution to prevent accidental state changes.
|
|
|
|
## 2. Production Environment Safety
|
|
Any action that targets a production environment must have a hard confirmation gate. Production actions must never run based on vague or ambiguous prompts. The user must provide explicit, unambiguous consent to proceed with a production deployment or modification.
|
|
|
|
## 3. Secret Redaction
|
|
To maintain a secure environment, all secrets, tokens, passwords, and sensitive keys must be strictly redacted from:
|
|
- System and application logs
|
|
- Tool return values/outputs
|
|
- Any form of persistent storage or console output
|
|
|
|
## 4. Read-Only First Policy
|
|
By default, MCP servers (such as `jenkins-mcp` and `ops-mcp`) operate in a **read-only** mode. Mutation capabilities are deny-by-default and fail-closed.
|
|
|
|
## 5. Mutation Gating
|
|
Any mutating action (e.g., Gitea issue creation from GlitchTip, or Jenkins builds) must be explicitly allowed by the execution profile.
|
|
- **Jenkins build triggers** are explicitly deferred for phase 1.
|
|
- **GlitchTip to Gitea issue filing** is documented as a gated, orchestrated workflow, not a direct unprompted automatic action.
|