explain_table

Explain table structure (alias for DESCRIBE).

SERVERMysql SOURCEmukul975/mysql-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-mysql-mcp-server/explain-table.md

WHAT IT DOES

What explain_table does on Mysql

AI agents call explain_table to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why explain_table is rated Low

This tool executes a DESCRIBE/EXPLAIN statement to inspect table structure and schema information. It has no side effects, does not modify data, and does not execute arbitrary code. The server description emphasizes 'read-only queries' which aligns with this classification.

From the tool's definition Tool name 'explain_table' with description 'Explain table structure (alias for DESCRIBE)' - DESCRIBE is a read-only SQL command that retrieves schema metadata without modifying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs explain_table safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For explain_table, this is the rule to start with:

explain_table Allowed

explain_table is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "explain_table": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql, apply this rule, and every explain_table call is checked against it from then on.

FAQ

Questions about explain_table

What does the explain_table tool do? +

Explain table structure (alias for DESCRIBE). It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on explain_table? +

Register the Mysql MCP server in PolicyLayer and add a rule for explain_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. Nothing to install.

What risk level is explain_table? +

explain_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit explain_table? +

Yes. Add a rate_limit block to the explain_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.

How do I block explain_table completely? +

Set action: deny in the PolicyLayer policy for explain_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.

What MCP server provides explain_table? +

explain_table is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 233 Mysql tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →