AI agents call 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.
This tool retrieves data without side effects. Even though SQL can be dangerous in general contexts, the read-only restriction eliminates Write, Destructive, Execute (arbitrary operations), and Financial risks. The only residual concern is information disclosure (low severity) depending on database sensitivity, but the tool itself performs a Read operation as defined in the classification scheme.
From the tool's definition Tool is described as 'Executes a read-only SQL query' and the server supports 'read-only queries'. The explicit read-only constraint means no data modification is possible.
Documented attack patterns abuse exactly the kind of access query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query:
{
"version": "1",
"default": "deny",
"tools": {
"query": {}
}
}query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Executes a read-only SQL query. 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 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.
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 MySQL MCP Server MCP server (xiangma9712/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MySQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.