We're evaluating how far to let KentiCopilot and MCP-driven workflows go beyond suggestions and into actual content or schema changes. The technical capability is moving quickly, but production write access raises governance questions that do not exist when the agent is read-only.
For teams using or planning to use KentiCopilot in production, what guardrails have worked well? I'm especially interested in separation between development, staging, and production; least-privilege access; required human approval for publishing or content-model changes; validation and rollback; and an audit trail that ties each action to the requester and instructions.
Do you allow any autonomous writes in production today? If so, which operations are permitted, and which changes always require an editor or developer to approve?