insert_data · MySQL MCP: Risk & Policy

WHAT IT DOES

What insert_data does on MySQL MCP

AI agents use insert_data 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.

WHY IT NEEDS A POLICY

Why insert_data needs a policy

This tool creates new records in database tables, which is a reversible write operation. It modifies data state but does not irreversibly delete or destroy information (hence not Destructive), nor does it execute arbitrary code or shell commands (hence not Execute).

From the tool's definition Tool name 'insert_data' with description '向表中插入数据' (insert data into table); sibling tools include delete_data and update_data, confirming a database mutation context.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_data Rate-limited

insert_data 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": {
    "insert_data": {
      "limits": [
        {
          "counter": "insert_data_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MySQL MCP, so you can run agents against it safely.

FAQ

Questions about insert_data

What does the insert_data tool do? +

向表中插入数据. 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 insert_data? +

Register the MySQL MCP server in PolicyLayer and add a rule for insert_data: 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 insert_data? +

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

Can I rate-limit insert_data? +

Yes. Add a rate_limit block to the insert_data 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 insert_data completely? +

Set action: deny in the PolicyLayer policy for insert_data. 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 insert_data? +

insert_data is provided by the MySQL MCP server (liu-creators/mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.