Execute a read-only SQL query against MySQL databases. Supports SELECT, SHOW, DESCRIBE, and EXPLAIN statements.
AI agents call mysql_query to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although this tool only permits read operations, it gains 'high' severity because it provides access to potentially sensitive business data across 'multiple MySQL databases' with 'enterprise data federation' per the server description. Misuse by an AI agent could expose confidential information, intellectual property, or personally identifiable data at scale.
From the tool's definition Tool description states 'Execute a read-only SQL query against MySQL databases. Supports SELECT, SHOW, DESCRIBE, and EXPLAIN statements.' The explicit 'read-only' restriction and enumerated statement types (SELECT, SHOW, DESCRIBE, EXPLAIN) confirm no data…
Attacks that exploit this kind of access
Execute a read-only SQL query against MySQL databases. Supports SELECT, SHOW, DESCRIBE, and EXPLAIN statements. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for mysql_query: 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.
mysql_query 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_query 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_query. 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_query is provided by the MySQL MCP Server MCP server (ttpears/mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
mysql_query 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 →