mysql_get_table_stats

THE RISK

Low Risk

Why mysql_get_table_stats needs a policy

This tool retrieves table statistics without creating, modifying, deleting, or executing code. It is a straightforward read operation that has no side effects and a minimal blast radius even if misused by an AI agent (an agent could learn table metadata but cannot alter data or trigger external operations).

From the tool's definition Tool name and description indicate retrieval of statistics ("row count, size, etc.") with no modification or deletion of data. The action is purely observational—querying metadata about a table structure and size.

Documented attack patterns abuse exactly the kind of access mysql_get_table_stats gives an agent:

POLICY

How to control mysql_get_table_stats

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_get_table_stats:

policy.json

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

mysql_get_table_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register MCP MySQL Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP MySQL Server tools

Execute mysql_query Execute a SQL query on the connected MySQL database Write mysql_disconnect Disconnect from the MySQL database Read mysql_describe_table Get the structure/schema of a specific table Read mysql_list_databases List all databases on the MySQL server Read mysql_list_tables List all tables in the current or specified database Read mysql_show_indexes Show indexes for a specific table Other mysql_connect Connect to a MySQL database with provided connection parameters

All 8 MCP MySQL Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mysql_get_table_stats

What does the mysql_get_table_stats tool do? +

Get statistics about a table (row count, size, etc.). It is categorised as a Read tool in the MCP MySQL Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_get_table_stats? +

Register the MCP MySQL Server MCP server in PolicyLayer and add a rule for mysql_get_table_stats: 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.

What risk level is mysql_get_table_stats? +

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

Can I rate-limit mysql_get_table_stats? +

Yes. Add a rate_limit block to the mysql_get_table_stats 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_get_table_stats completely? +

Set action: deny in the PolicyLayer policy for mysql_get_table_stats. 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_get_table_stats? +

mysql_get_table_stats 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.

Enforce policy on every MCP MySQL Server tool call.

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.

CHECK YOUR STACK →