Analyze table statistics including row count, size, and column information.
AI agents call analyze_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 performs a query operation that retrieves and reports on table metadata and statistics. No data is created, modified, deleted, or destroyed. No code execution or external operations are triggered. The analysis is purely informational, making it a straightforward Read category tool with low severity and high confidence.
From the tool's definition Tool description states 'Analyze table statistics including row count, size, and column information' — a read-only operation that retrieves metadata and statistics without modifying data.
Attacks that exploit this kind of access
Analyze table statistics including row count, size, and column information. 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 analyze_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.
analyze_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 analyze_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 analyze_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.
analyze_table is provided by the MCP MySQL Server MCP server (kami2k1/mcp-mysql). 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 →