Validate JSON columns and data.
AI agents call mysql_json_validation to retrieve information from Mysql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
JSON validation is a read-only operation that examines and verifies data structure without creating, modifying, or deleting any records. It has no destructive or reversible write side effects. Blast radius is minimal — at worst, incorrect validation logic might cause false positives/negatives in data assessment, but no data is changed or executed as code. This aligns with the Read category.
From the tool's definition Tool name and description indicate 'Validate JSON columns and data' — a validation/inspection operation with no modification or side effects. The server description emphasizes 'read-only queries' and 'monitoring' as core functions.
Documented attack patterns abuse exactly the kind of access mysql_json_validation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_json_validation:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_json_validation": {}
}
}mysql_json_validation 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.
Validate JSON columns and data. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_json_validation: 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. Nothing to install.
mysql_json_validation 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_validation 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_validation. 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_validation is provided by the Mysql MCP server (mukul975/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, 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.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.