描述表结构 Args: table: 表名 database: 数据库名称 (可选,默认使用当前连接的数据库) Returns: 表结构描述的JSON字符串
AI agents call mysql_describe_table 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 tool queries database metadata (table structure/schema) and returns information without side effects. It is a retrieval operation analogous to DESCRIBE or SHOW COLUMNS in SQL, which are read-only introspection commands. The blast radius of misuse is minimal—an agent could learn schema details but cannot modify data, execute arbitrary code, or cause financial impact.
From the tool's definition Tool name 'mysql_describe_table' and description '描述表结构' (describe table structure) indicate it retrieves and returns table schema metadata as JSON. Arguments are table name and optional database name.
Documented attack patterns abuse exactly the kind of access mysql_describe_table 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_describe_table:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_describe_table": {}
}
} mysql_describe_table 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: table: 表名 database: 数据库名称 (可选,默认使用当前连接的数据库) 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_describe_table: 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_describe_table 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_describe_table 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_describe_table. 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_describe_table 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.