# mysql_migration_record Record a migration in the schema version tracking table with status Agent View of the PolicyLayer registry record for `mysql_migration_record`. HTML page: https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-migration-record ## Facts - Tool: `mysql_migration_record` - Server: Mysql Mcp (`oci:docker.io/writenotenow/mysql-mcp:v1.0.0`) — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp.md - Homepage: https://github.com/neverinfamous/mysql-mcp.git - Risk category: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "mysql_migration_record", "arguments": {} } } ``` ## Why mysql_migration_record is rated Medium This tool writes/creates a migration record in a schema version tracking table. It is a data creation/modification operation (recording status), which is reversible (the record can be deleted or updated). It does not execute arbitrary SQL, delete data, or move money. Severity is medium because incorrect migration records could corrupt schema version history and cause deployment issues. From the tool's own definition: "Record a migration in the schema version tracking table with status" ## Use case AI agents use mysql_migration_record to create or update resources in Mysql Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mysql Mcp environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mysql Mcp: ```json { "version": "1", "default": "deny", "tools": { "mysql_migration_record": { "limits": [ { "counter": "mysql_migration_record_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## Other tools on Mysql Mcp (222) - `mysql_audit_restore_backup` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-audit-restore-backup.md - `mysql_cascade_simulator` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-cascade-simulator.md - `mysql_doc_drop_collection` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-doc-drop-collection.md - `mysql_doc_remove` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-doc-remove.md - `mysql_drop_partition` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-partition.md - `mysql_drop_schema` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-schema.md - `mysql_drop_table` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-table.md - `mysql_drop_view` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-drop-view.md - `mysql_event_drop` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-event-drop.md - `mysql_force_index` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-force-index.md - `mysql_fulltext_drop` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-fulltext-drop.md - `mysql_json_remove` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-json-remove.md - `mysql_migration_rollback` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-migration-rollback.md - `mysql_role_drop` — Destructive — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-role-drop.md - `mysql_analyze_table` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-analyze-table.md - `mysql_create_dump` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-create-dump.md - `mysql_event_create` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-event-create.md - `mysql_flush_tables` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-flush-tables.md - `mysql_json_merge` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-json-merge.md - `mysql_migration_apply` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-migration-apply.md - `mysql_optimize_table` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-optimize-table.md - `mysql_spatial_intersection` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-intersection.md - `mysql_spatial_transform` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-spatial-transform.md - `mysql_stats_row_number` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-stats-row-number.md - `mysql_transaction_begin` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-transaction-begin.md - `mysql_transaction_execute` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-transaction-execute.md - `mysqlsh_run_script` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysqlsh-run-script.md - `proxysql_commands` — Execute — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/proxysql-commands.md - `mysql_audit_diff_backup` — Read — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-audit-diff-backup.md - `mysql_audit_list_backups` — Read — https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp/mysql-audit-list-backups.md - …and 192 more: https://policylayer.com/tools/io-github-neverinfamous-mysql-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-neverinfamous-mysql-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-neverinfamous-mysql-mcp