mysql_explain
Get query execution plan using EXPLAIN.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-explain.md
What mysql_explain does on Mysql Mcp
AI agents call mysql_explain to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_explain is rated Low
EXPLAIN is a diagnostic tool that retrieves metadata about how MySQL will execute a query. It does not execute the query, modify data, delete records, or trigger external side effects. It is purely informational and safe to classify as Read. Severity is low because misuse of EXPLAIN (e.g., on complex queries) would at worst consume CPU for planning but cannot corrupt data or cause financial harm.
From the tool's definition Tool name 'mysql_explain' and description 'Get query execution plan using EXPLAIN' indicate a read-only operation. EXPLAIN is a MySQL statement that analyzes and displays query execution plans without modifying data or executing the query itself.
Attacks that exploit this kind of access
The rule that runs mysql_explain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_explain, this is the rule to start with:
mysql_explain is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_explain call is checked against it from then on.
Questions about mysql_explain
Get query execution plan using EXPLAIN. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_explain: 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.
mysql_explain is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mysql_explain 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_explain. 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_explain is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). 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.
This server
Across the catalogue