get_mysql_databases

What get_mysql_databases does on 20i MCP Server

AI agents call get_mysql_databases to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_mysql_databases is rated Low

This is a Read operation: it queries and retrieves MySQL database metadata/list for a hosting package without creating, modifying, or deleting anything. Severity is medium (not low) because unauthorized access to database information in a hosting context could expose sensitive customer data, and an AI agent with access could enumerate valuable targets. Confidence is high because the intent is unambiguous.

From the tool's definition Tool name explicitly states 'get' and description says 'Get MySQL databases' — retrieves data with no modification capability. However, databases often contain sensitive customer data (PII, credentials, business records).

The rule that runs get_mysql_databases safely

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

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

Questions about get_mysql_databases