AI agents call describe_table to retrieve information from MySQL-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries table schema (columns, types, constraints, etc.) and returns information for inspection. It performs no modifications, no code execution, and no destructive operations. It is a standard database introspection operation with minimal risk if exposed to an AI agent, as the worst outcome is information disclosure about table structure.
From the tool's definition Tool name is 'describe_table' and description states 'View schema information for a specific table' — a read-only operation that retrieves metadata without modifying data.
Attacks that exploit this kind of access
View schema information for a specific table. It is categorised as a Read tool in the MySQL-MCP MCP Server, which means it retrieves data without modifying state.
Register the MySQL- MCP server in PolicyLayer and add a rule for 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.
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 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 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.
describe_table is provided by the MySQL- MCP server (zajtools/zaj-mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →