mysql_json_search
Search for a string value in JSON columns and return matching paths.
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-json-search.md
What mysql_json_search does on Mysql Mcp
AI agents call mysql_json_search to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_json_search is rated Low
This tool retrieves and queries data from JSON columns to find matching paths. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. It is a straightforward read operation analogous to a SELECT query with a WHERE clause filtering JSON data.
From the tool's definition Tool name contains 'search' and description states it will 'Search for a string value in JSON columns and return matching paths' — a pure query operation with no data modification or execution of arbitrary code.
Attacks that exploit this kind of access
The rule that runs mysql_json_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_json_search, this is the rule to start with:
mysql_json_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_json_search call is checked against it from then on.
Questions about mysql_json_search
Search for a string value in JSON columns and return matching paths. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_json_search: 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. Nothing to install.
mysql_json_search 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_json_search 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_json_search. 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_json_search is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue