update_data · MCP MySQL Server MCP: Risk & Policy

WHAT IT DOES

What update_data does on MCP MySQL Server

AI agents use update_data to create or update resources in MCP MySQL Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP MySQL Server environment.

WHY IT NEEDS A POLICY

Why update_data needs a policy

This tool modifies existing data within a table but does not delete or destroy records. Updates are typically reversible through transaction rollback or additional updates, making it Write rather than Destructive. Severity is medium because misuse by an AI agent (e.g., updating all rows with incorrect values) could corrupt data but remains recoverable.

From the tool's definition Tool name 'update_data' and description 'Update data in a table' indicate data modification. Server description confirms 'data manipulation' capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_data Rate-limited

update_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": {
    "update_data": {
      "limits": [
        {
          "counter": "update_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 MCP MySQL Server, so you can run agents against it safely.

FAQ

Questions about update_data

What does the update_data tool do? +

Update data in a table. It is categorised as a Write tool in the MCP MySQL Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_data? +

Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for update_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 MCP MySQL Server. Nothing to install.

What risk level is update_data? +

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

Can I rate-limit update_data? +

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

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

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