Get the structure/schema of a specific table
AI agents call mysql_describe_table 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 schema information (columns, data types, constraints) from a database table. It has no side effects, does not modify data, does not execute arbitrary queries, and does not delete or create objects. It is a pure read operation that queries the information schema, similar to DESCRIBE TABLE or SHOW COLUMNS statements.
From the tool's definition Tool name 'mysql_describe_table' and description 'Get the structure/schema of a specific table' indicate retrieval of metadata about table schema without modification or execution of arbitrary operations.
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 MCP MySQL 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.
Get the structure/schema of a specific table. 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_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 MCP MySQL 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 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.