List all tables in the current or specified database
AI agents call mysql_list_tables to retrieve information from MCP MySQL Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves metadata about database tables. It has no side effects, does not execute arbitrary queries, and does not modify, delete, or create any data. It is purely informational, similar to SHOW TABLES in SQL. Blast radius is minimal as misuse would only expose database schema structure, not sensitive data values.
From the tool's definition Tool name 'mysql_list_tables' and description 'List all tables in the current or specified database' indicate a schema inspection operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access mysql_list_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP MySQL Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_list_tables:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_list_tables": {}
}
} mysql_list_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all tables in the current or specified database. It is categorised as a Read tool in the MCP MySQL Server MCP Server, which means it retrieves data without modifying state.
Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for mysql_list_tables: 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 MySQL Server. Nothing to install.
mysql_list_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mysql_list_tables 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 mysql_list_tables. 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.
mysql_list_tables is provided by the MCP MySQL Server MCP server (sajithrw/mcp-mysql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP MySQL Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 MCP MySQL Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.