use_database · MySQL MCP: Risk & Policy

WHAT IT DOES

What use_database does on MySQL MCP

AI agents invoke use_database to trigger actions in MySQL MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why use_database needs a policy

This tool switches the active database context for subsequent queries. It doesn't read, write, or destroy data on its own, but it is an operational action that affects the execution environment — subsequent SQL operations will target the newly selected database.

From the tool's definition 切换到指定的数据库 (Switch to the specified database); part of a server designed to 'directly perform database operations'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

use_database Rate-limited

use_database stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "use_database": {
      "limits": [
        {
          "counter": "use_database_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 use_database

What does the use_database tool do? +

切换到指定的数据库. It is categorised as a Execute tool in the MySQL MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on use_database? +

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

use_database is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit use_database? +

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

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

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