mysql-query
Executes a MySQL query and returns structured tabular output.
This record as markdown: /tools/io-github-dave-london-pare-search/mysql-query.md
What mysql-query does on Search
AI agents invoke mysql-query to trigger actions in Search. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why mysql-query is rated High
Executing arbitrary SQL queries can include SELECT (Read), INSERT/UPDATE (Write), DELETE/DROP (Destructive), or stored procedure calls (Execute). Since the description says 'executes a MySQL query' without restriction, the worst-case is Destructive or Execute. However, without explicit mention of write/delete capabilities, Execute is the most appropriate catch-all for running arbitrary database queries.
From the tool's definition 'Executes a MySQL query' — the tool runs arbitrary SQL against a MySQL database and returns results.
Attacks that exploit this kind of access
The rule that runs mysql-query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql-query, this is the rule to start with:
mysql-query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Search, apply this rule, and every mysql-query call is checked against it from then on.
Questions about mysql-query
Executes a MySQL query and returns structured tabular output. It is categorised as a Execute tool in the Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Search 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 Search. Nothing to install.
mysql-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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 Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
Across the catalogue