by MigratrixCommunityDatabase change control for AgentOne: read schemas, write change scripts, run the pre-flight check, ask approvers, watch the rollout and read the audit ledger, with the permissions of the person who connected it.
Migratrix is change control for production databases: SQL Server, Oracle, PostgreSQL, MySQL and MariaDB. Teams write change scripts, promote them through environments with approvals, and get an automatic, verified rollback for every change. This connector lets AgentOne take part in that process with exactly the permissions of the person who connected it, and never more.
What AgentOne can do:
AgentOne can never do, whatever the person's permissions allow: approve a change, change approval rules, roles, environments or pipelines, write a rollback, execute or roll back in an environment that requires approval, read or write database credentials, or write to data. Administrators set a level per environment (nothing, read, propose or execute) and can pause every AgentOne connection with one switch. Every call is recorded in the audit ledger, marked as made through AgentOne.
Schemas and rows stay inside the customer's network. A second, optional endpoint is served by the Migratrix Executor there and is covered by the same consent. This listing is the control-plane endpoint, which any AgentOne installation can reach.
Read-only tools are marked readOnlyHint. Tools that run or roll back a change are marked destructiveHint, so AgentOne asks before using them.