mysql_innodb_lock_waits
Show detailed InnoDB lock wait information.
This record as markdown: /tools/mukul975-mysql-mcp-server/mysql-innodb-lock-waits.md
What mysql_innodb_lock_waits does on Mysql
AI agents call mysql_innodb_lock_waits to retrieve information from Mysql without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mysql_innodb_lock_waits is rated Low
This tool queries and displays InnoDB lock wait information, which is a read-only monitoring/diagnostic operation. It retrieves current lock wait state from MySQL internal tables (e.g., information_schema or performance_schema) without modifying any data. The server description also emphasizes 'read-only queries' and 'server monitoring', consistent with this classification.
From the tool's definition 'Show detailed InnoDB lock wait information' — purely retrieves and displays lock wait data with no side effects
Attacks that exploit this kind of access
The rule that runs mysql_innodb_lock_waits safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_innodb_lock_waits, this is the rule to start with:
mysql_innodb_lock_waits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mysql, apply this rule, and every mysql_innodb_lock_waits call is checked against it from then on.
Questions about mysql_innodb_lock_waits
Show detailed InnoDB lock wait information. 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_innodb_lock_waits: 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_innodb_lock_waits 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_innodb_lock_waits 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_innodb_lock_waits. 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_innodb_lock_waits 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.
More on Mysql, and thousands of servers like it.
This server
Across the catalogue