mysql_innodb_lock_waits

Show detailed InnoDB lock wait information.

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-mcp-windows-automation/mysql-innodb-lock-waits.md

WHAT IT DOES

What mysql_innodb_lock_waits does on Mcp Windows

AI agents call mysql_innodb_lock_waits to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mysql_innodb_lock_waits is rated Low

The tool retrieves and displays InnoDB lock wait information from MySQL. This is a read/query operation with no side effects - it only shows diagnostic information about current lock waits without modifying any data or system state.

From the tool's definition Show detailed InnoDB lock wait information

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_innodb_lock_waits safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, 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 Allowed

mysql_innodb_lock_waits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every mysql_innodb_lock_waits call is checked against it from then on.

FAQ

Questions about mysql_innodb_lock_waits

What does the mysql_innodb_lock_waits tool do? +

Show detailed InnoDB lock wait information. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_innodb_lock_waits? +

Register the Mcp Windows 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 Mcp Windows. Nothing to install.

What risk level is mysql_innodb_lock_waits? +

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

Can I rate-limit mysql_innodb_lock_waits? +

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.

How do I block mysql_innodb_lock_waits completely? +

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.

What MCP server provides mysql_innodb_lock_waits? +

mysql_innodb_lock_waits is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Windows, and thousands of servers like it.

This server

All 441 Mcp Windows tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →