This record as markdown: /tools/mukul975-mysql-mcp-server/mysql-use-database.md
What mysql_use_database does on Mysql
AI agents invoke mysql_use_database to trigger actions in Mysql. 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 mysql_use_database is rated High
Switching the active database context is not a pure read operation; it changes session state and affects all subsequent queries executed in that session. This is an Execute-level action because it alters the operational context of the database connection, potentially redirecting subsequent queries to a different (possibly sensitive) database.
From the tool's definition 'Switch to a different database' — changes the active database context for the session, triggering an external state change in the MySQL connection
Attacks that exploit this kind of access
The rule that runs mysql_use_database safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_use_database, this is the rule to start with:
mysql_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql, apply this rule, and every mysql_use_database call is checked against it from then on.
Questions about mysql_use_database
Switch to a different database. It is categorised as a Execute tool in the Mysql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_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. Nothing to install.
mysql_use_database is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mysql_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.
Set action: deny in the PolicyLayer policy for mysql_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.
mysql_use_database is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
Across the catalogue