use_database · MySQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What use_database does on MySQL MCP Server

AI agents invoke use_database to trigger actions in MySQL MCP Server. 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 executes a MySQL USE statement to switch the active database context for the connection. It is not a simple read, nor does it write/delete data, but it triggers an external operation (context switch on the database connection) that affects all subsequent queries. Misuse could redirect an AI agent's queries to an unintended database, potentially exposing or modifying wrong data.

From the tool's definition USE 切换库 — switches the active database context

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 Server, so you can run agents against it safely.

FAQ

Questions about use_database

What does the use_database tool do? +

USE 切换库. It is categorised as a Execute tool in the MySQL MCP Server 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 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 Server. 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 MCP server (yclenove/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

use_database is one line of MySQL MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →