Execute a SELECT/SHOW/DESCRIBE/EXPLAIN query and return results. Use this for reading data.
AI agents call query to retrieve information from MCP Server MySQL without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is limited to SELECT, SHOW, DESCRIBE, and EXPLAIN statements, which are read-only operations that query and retrieve data without side effects. While the tool operates on a database, it cannot create, modify, or delete data. The blast radius of misuse is minimal—an attacker could exfiltrate data but cannot corrupt or destroy it.
From the tool's definition Tool description explicitly states 'Execute a SELECT/SHOW/DESCRIBE/EXPLAIN query and return results. Use this for reading data.' SELECT, SHOW, DESCRIBE, and EXPLAIN are all read-only SQL operations that retrieve information without modifying database state.
Attacks that exploit this kind of access
Execute a SELECT/SHOW/DESCRIBE/EXPLAIN query and return results. Use this for reading data. It is categorised as a Read tool in the MCP Server MySQL MCP Server, which means it retrieves data without modifying state.
Register the MCP Server MySQL MCP server in PolicyLayer and add a rule for 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 MCP Server MySQL. Nothing to install.
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 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 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.
query is provided by the MCP Server MySQL MCP server (nilsir/mcp-server-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →