backup_table · MCP MySQL Server MCP: Risk & Policy

WHAT IT DOES

What backup_table does on MCP MySQL Server

AI agents use backup_table 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 backup_table needs a policy

Backup operations are Write category because they create new data structures (backup copies) without being irreversible like Destructive operations. However, the severity is high because backups can consume significant storage resources, potentially impact database performance, and if misused could create unauthorized data copies or expose sensitive information.

From the tool's definition The tool creates a backup copy of a table, which is a reversible write operation that modifies the database state by adding new data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backup_table Rate-limited

backup_table 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": {
    "backup_table": {
      "limits": [
        {
          "counter": "backup_table_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 backup_table

What does the backup_table tool do? +

Create a backup copy of 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 backup_table? +

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

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

Can I rate-limit backup_table? +

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

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

backup_table 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.