mysql_describe_table

Get detailed information about a table

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

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/io-github-neverinfamous-mysql-mcp/mysql-describe-table.md

WHAT IT DOES

What mysql_describe_table does on Mysql Mcp

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

RISK

Why mysql_describe_table is rated Low

This tool fetches table structure information (columns, types, constraints, etc.) which is a read-only operation with no side effects. It does not create, modify, delete, execute code, or affect data. The blast radius of misuse is minimal—an agent could only learn table structure, which is typically non-sensitive or already discoverable.

From the tool's definition Tool name 'mysql_describe_table' and description 'Get detailed information about a table' indicate a query operation that retrieves schema metadata without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_describe_table safely

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

mysql_describe_table Allowed

mysql_describe_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": {
    "mysql_describe_table": {}
  }
}

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

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

FAQ

Questions about mysql_describe_table

What does the mysql_describe_table tool do? +

Get detailed information about a table. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_describe_table? +

Register the Mysql 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. Nothing to install.

What risk level is mysql_describe_table? +

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

Can I rate-limit mysql_describe_table? +

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.

How do I block mysql_describe_table completely? +

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.

What MCP server provides mysql_describe_table? +

mysql_describe_table is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). 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 223 Mysql tools →

Across the catalogue

The MCP Attack Database →

Guides

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