mysql_migration_record

Record a migration in the schema version tracking table with status

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-migration-record.md

WHAT IT DOES

What mysql_migration_record does on Mysql Mcp

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.

RISK

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 definition Record a migration in the schema version tracking table with status

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_migration_record safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_migration_record, this is the rule to start with:

mysql_migration_record Rate-limited

mysql_migration_record stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_migration_record": {
      "limits": [
        {
          "counter": "mysql_migration_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_migration_record call is checked against it from then on.

FAQ

Questions about mysql_migration_record

What does the mysql_migration_record tool do? +

Record a migration in the schema version tracking table with status. It is categorised as a Write tool in the Mysql Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mysql_migration_record? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_migration_record: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mysql Mcp. Nothing to install.

What risk level is mysql_migration_record? +

mysql_migration_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mysql_migration_record? +

Yes. Add a rate_limit block to the mysql_migration_record rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block mysql_migration_record completely? +

Set action: deny in the PolicyLayer policy for mysql_migration_record. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides mysql_migration_record? +

mysql_migration_record is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →