mysqlsh_import_json
Import JSON documents from a file using util.importJson(). Supports NDJSON (one JSON object per line) and multi-line JSON objects (not JSON arrays). REQUIRES X Protocol (port 33060).
This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysqlsh-import-json.md
What mysqlsh_import_json does on Mysql Mcp
AI agents use mysqlsh_import_json to create or update resources in Mysql Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mysql Mcp environment.
Why mysqlsh_import_json is rated Medium
This tool writes/creates data by importing JSON into MySQL. While not destructive (no deletion), it modifies the database by adding or loading document data. The severity is high because an attacker could import malicious JSON that violates schema constraints, triggers unexpected application logic, or consumes excessive storage/memory.
From the tool's definition Tool imports JSON documents from a file, which creates or loads new data into the database via util.importJson(). The description explicitly states it 'Import[s] JSON documents from a file', indicating data ingestion that modifies the database state.
Attacks that exploit this kind of access
The rule that runs mysqlsh_import_json 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 mysqlsh_import_json, this is the rule to start with:
mysqlsh_import_json stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 mysqlsh_import_json call is checked against it from then on.
Questions about mysqlsh_import_json
Import JSON documents from a file using util.importJson(). Supports NDJSON (one JSON object per line) and multi-line JSON objects (not JSON arrays). REQUIRES X Protocol (port 33060). It is categorised as a Write tool in the Mysql Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mysql MCP server in PolicyLayer and add a rule for mysqlsh_import_json: 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.
mysqlsh_import_json is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mysqlsh_import_json 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 mysqlsh_import_json. 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.
mysqlsh_import_json 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