AI agents call get_tables_info 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 retrieves table structure metadata (schema information) from a MySQL database. It performs read-only operations that return information about tables without side effects, modifications, or code execution. Even though it shares a server with execute_sql (which would be Execute/Destructive), this specific tool is purely informational.
From the tool's definition Tool name 'get_tables_info' and description '获取数据库表结构信息' (get database table structure information) indicate retrieval of metadata about table schemas without modification or execution of queries.
Documented attack patterns abuse exactly the kind of access get_tables_info 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 get_tables_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_tables_info": {}
}
}get_tables_info 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.
获取数据库表结构信息. 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 get_tables_info: 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.
get_tables_info 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 get_tables_info 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 get_tables_info. 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.
get_tables_info is provided by the MCP MySQL Server MCP server (tickhaijun/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 MCP MySQL Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 MCP MySQL Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.