mysql_check

Connect to a MySQL/MariaDB server and read the server greeting to extract the server version. Does not authenticate. Useful for verifying database server reachability and version.

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/mysql-check.md

WHAT IT DOES

What mysql_check does on Mcp Nettools

AI agents call mysql_check to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mysql_check is rated Low

The tool connects to a MySQL/MariaDB server and reads the server greeting to extract version information. It performs no authentication, executes no queries, modifies no data, and triggers no external operations beyond establishing a connection to read response metadata.

From the tool's definition Tool description explicitly states it 'read[s] the server greeting' and 'does not authenticate', performing version extraction without modification or execution of queries. This is a passive reconnaissance operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_check safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_check, this is the rule to start with:

mysql_check Allowed

mysql_check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_check": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about mysql_check

What does the mysql_check tool do? +

Connect to a MySQL/MariaDB server and read the server greeting to extract the server version. Does not authenticate. Useful for verifying database server reachability and version. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_check? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for mysql_check: 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 Mcp Nettools. Nothing to install.

What risk level is mysql_check? +

mysql_check is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_check? +

Yes. Add a rate_limit block to the mysql_check 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_check completely? +

Set action: deny in the PolicyLayer policy for mysql_check. 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_check? +

mysql_check is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →