mysql-list-databases

Lists all MySQL databases with structured output.

SERVERBuild SOURCEDave-London/Pare

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-dave-london-build/mysql-list-databases.md

WHAT IT DOES

What mysql-list-databases does on Build

AI agents call mysql-list-databases to retrieve information from Build 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-list-databases is rated Low

This tool performs database discovery/enumeration without modifying data, executing code, or triggering external operations. It retrieves information about existing databases, which is a Read operation. The severity is low because listing databases has minimal blast radius—it only exposes metadata about available databases without granting access to their contents or ability to modify them.

From the tool's definition mysql-list-databases: Lists all MySQL databases with structured output. The verb 'Lists' and the passive nature of database enumeration indicate a read-only operation with no modification or execution of code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql-list-databases safely

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

mysql-list-databases Allowed

mysql-list-databases 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-list-databases": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every mysql-list-databases call is checked against it from then on.

FAQ

Questions about mysql-list-databases

What does the mysql-list-databases tool do? +

Lists all MySQL databases with structured output. It is categorised as a Read tool in the Build MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql-list-databases? +

Register the Build MCP server in PolicyLayer and add a rule for mysql-list-databases: 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 Build. Nothing to install.

What risk level is mysql-list-databases? +

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

Can I rate-limit mysql-list-databases? +

Yes. Add a rate_limit block to the mysql-list-databases 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-list-databases completely? +

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

mysql-list-databases is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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