mysql_cluster_instances

List all instances in the InnoDB Cluster.

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

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/io-github-neverinfamous-mysql-mcp/mysql-cluster-instances.md

WHAT IT DOES

What mysql_cluster_instances does on Mysql Mcp

AI agents call mysql_cluster_instances 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.

RISK

Why mysql_cluster_instances is rated Low

This tool retrieves cluster metadata without modifying data, executing code, or triggering side effects. It is a straightforward read operation that queries the state of InnoDB Cluster instances. Severity is low because unauthorized access reveals operational topology but does not enable direct damage.

From the tool's definition Tool name 'mysql_cluster_instances' and description 'List all instances in the InnoDB Cluster' indicate a query/retrieval operation with no modification or execution of external commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mysql_cluster_instances Allowed

mysql_cluster_instances 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_cluster_instances": {}
  }
}

ALLOW ONLY 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_cluster_instances call is checked against it from then on.

FAQ

Questions about mysql_cluster_instances

What does the mysql_cluster_instances tool do? +

List all instances in the InnoDB Cluster. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_cluster_instances? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_cluster_instances: 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_cluster_instances? +

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

Can I rate-limit mysql_cluster_instances? +

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

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

mysql_cluster_instances 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 →

Across the catalogue

The MCP Attack Database →

Guides

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