AI agents call query-data 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.
The tool name 'query-data' and the server's explicit mention of 'querying' functionality indicate this retrieves data without side effects. However, confidence is reduced to 0.75 because the tool description is empty and we must infer intent from name and context alone.
From the tool's definition Tool name 'query-data' and server description indicating 'querying' capabilities; sibling tools include destructive operations (delete-data, drop-table) which contextualize this as a read operation.
Documented attack patterns abuse exactly the kind of access query-data 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-data:
{
"version": "1",
"default": "deny",
"tools": {
"query-data": {}
}
}query-data 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.
query-data. 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-data: 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-data 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-data 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-data. 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-data is provided by the MySQL MCP Server MCP server (log6262635/mcp-mysql). 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.
7 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.