获取数据库中的表列表，支持筛选和限制结果数量 Args: database: 数据库名称 (可选，默认使用当前连接的数据库) pattern: 表名匹配模式 (可选, 例如 '%user%') limit: 返回结果的最大数量 (默认100，设为0表示无限制) exclude_views: 是否排除视图 (默认为False) Returns: 表列表的JSON字符串
AI agents call mysql_show_tables to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward metadata query operation that retrieves schema information (table names) from a MySQL database. It has no side effects, cannot modify or delete data, and only returns informational results. The parameters (database, pattern, limit, exclude_views) are all read-only filters. This is a classic Read category tool with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'mysql_show_tables' and description explicitly states it 'gets a list of tables in a database' with filtering and limit options. Returns 'JSON string of table list'. No data modification, deletion, or execution of arbitrary code is possible.
Documented attack patterns abuse exactly the kind of access mysql_show_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_show_tables:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_show_tables": {}
}
}mysql_show_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.
获取数据库中的表列表，支持筛选和限制结果数量 Args: database: 数据库名称 (可选，默认使用当前连接的数据库) pattern: 表名匹配模式 (可选, 例如 '%user%') limit: 返回结果的最大数量 (默认100，设为0表示无限制) exclude_views: 是否排除视图 (默认为False) Returns: 表列表的JSON字符串. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for mysql_show_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 MySQL MCP Server. Nothing to install.
mysql_show_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_show_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_show_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_show_tables is provided by the MySQL MCP Server MCP server (mangooer/mysql-mcp-server-sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MySQL MCP 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.
12 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.