Show current table locks and waiting processes.
AI agents call mysql_table_locks to retrieve information from Mysql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and displays current lock state and process information from the MySQL server. It has no side effects—it does not create, modify, delete, or execute any operations. The description explicitly uses 'Show', which is a read operation. Even though the sibling tools include destructive operations (drop_event, alter_event), this particular tool is purely informational for monitoring purposes.
From the tool's definition Tool name 'mysql_table_locks' and description 'Show current table locks and waiting processes' indicate a querying/monitoring operation that retrieves status information about locks without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access mysql_table_locks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mysql, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_table_locks:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_table_locks": {}
}
}mysql_table_locks 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.
Show current table locks and waiting processes. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.
Register the Mysql MCP server in PolicyLayer and add a rule for mysql_table_locks: 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. Nothing to install.
mysql_table_locks 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 mysql_table_locks 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 mysql_table_locks. 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.
mysql_table_locks is provided by the Mysql MCP server (mukul975/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mysql, 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.
233 Mysql tools catalogued and risk-classified — across an index of 43,000+ MCP servers.