AI agents call count_tables to retrieve information from MySQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database schema information (table count) without any side effects. It is a read-only operation that does not create, modify, delete, execute, or commit financial transactions. The action is purely informational and poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'count_tables' and description 'Get the total number of tables in the database' indicate a query operation that retrieves metadata without modifying data.
Documented attack patterns abuse exactly the kind of access count_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for count_tables:
{
"version": "1",
"default": "deny",
"tools": {
"count_tables": {}
}
}count_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the total number of tables in the database. It is categorised as a Read tool in the MySQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for count_tables: 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 Server. Nothing to install.
count_tables 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 count_tables 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 count_tables. 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.
count_tables is provided by the MySQL MCP Server MCP server (leonmelamud/mysql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MySQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.