mysql_json_merge

Merge two JSON documents using JSON_MERGE_PATCH or JSON_MERGE_PRESERVE.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-json-merge.md

WHAT IT DOES

What mysql_json_merge does on Mysql Mcp

AI agents invoke mysql_json_merge to trigger actions in Mysql Mcp. 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.

RISK

Why mysql_json_merge is rated High

This tool executes MySQL JSON merge functions (JSON_MERGE_PATCH or JSON_MERGE_PRESERVE) on the database server. While it appears to be a read/compute operation that combines JSON documents, it runs database functions whose side effects depend on arguments and context. It does not clearly create or modify stored data on its own, but it executes server-side operations.

From the tool's definition Merge two JSON documents using JSON_MERGE_PATCH or JSON_MERGE_PRESERVE

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_json_merge 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_merge, this is the rule to start with:

mysql_json_merge Rate-limited

mysql_json_merge 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_json_merge": {
      "limits": [
        {
          "counter": "mysql_json_merge_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_json_merge call is checked against it from then on.

FAQ

Questions about mysql_json_merge

What does the mysql_json_merge tool do? +

Merge two JSON documents using JSON_MERGE_PATCH or JSON_MERGE_PRESERVE. It is categorised as a Execute tool in the Mysql Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mysql_json_merge? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_json_merge: 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.

What risk level is mysql_json_merge? +

mysql_json_merge is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mysql_json_merge? +

Yes. Add a rate_limit block to the mysql_json_merge 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.

How do I block mysql_json_merge completely? +

Set action: deny in the PolicyLayer policy for mysql_json_merge. 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.

What MCP server provides mysql_json_merge? +

mysql_json_merge 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.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →